Lines Matching +full:clock +full:- +full:measure

1 .. SPDX-License-Identifier: GPL-2.0
29 Multigrain timestamps aim to remedy this by selectively using fine-grained
31 coarse-grained time does not cause a change.
56 not affected and always use the coarse-grained value (subject to the floor).
63 programs measure timestamps in order to determine whether source files might be
83 of the realtime clock. If that occurs at an inopportune time, then timestamps
91 atime will always use coarse-grained timestamps.
96 This ensures tight cache coherency for use-cases like NFS, without sacrificing
101 It's not sufficient to simply use fine or coarse-grained timestamps based on
103 timestamp, and then a second file modified later could get a coarse-grained one
110 order. To avoid problems with realtime clock jumps, the floor is managed as a
111 monotonic ktime_t, and the values are converted to realtime clock values as
117 ctime values from the local clock. This is in contrast to network filesystems
121 fstype->fs_flags in order to opt-in, providing the ctime is only ever set via
122 inode_set_ctime_current(). If the filesystem has a ->getattr routine that