diff options
author | Steven Whitehouse <swhiteho@redhat.com> | 2008-09-18 13:53:59 +0100 |
---|---|---|
committer | Steven Whitehouse <swhiteho@redhat.com> | 2008-09-18 13:53:59 +0100 |
commit | 719ee344675c2efed9115934f19aa66a526b6e5b (patch) | |
tree | 7f9502d696a09eaf5eba0a0d3fa35557ffd3c503 /net/irda | |
parent | 37ec89e83c4ca98323fe74f139301ff3949cfdb6 (diff) | |
download | lwn-719ee344675c2efed9115934f19aa66a526b6e5b.tar.gz lwn-719ee344675c2efed9115934f19aa66a526b6e5b.zip |
GFS2: high time to take some time over atime
Until now, we've used the same scheme as GFS1 for atime. This has failed
since atime is a per vfsmnt flag, not a per fs flag and as such the
"noatime" flag was not getting passed down to the filesystems. This
patch removes all the "special casing" around atime updates and we
simply use the VFS's atime code.
The net result is that GFS2 will now support all the same atime related
mount options of any other filesystem on a per-vfsmnt basis. We do lose
the "lazy atime" updates, but we gain "relatime". We could add lazy
atime to the VFS at a later date, if there is a requirement for that
variant still - I suspect relatime will be enough.
Also we lose about 100 lines of code after this patch has been applied,
and I have a suspicion that it will speed things up a bit, even when
atime is "on". So it seems like a nice clean up as well.
From a user perspective, everything stays the same except the loss of
the per-fs atime quantum tweekable (ought to be per-vfsmnt at the very
least, and to be honest I don't think anybody ever used it) and that a
number of options which were ignored before now work correctly.
Please let me know if you've got any comments. I'm pushing this out
early so that you can all see what my plans are.
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'net/irda')
0 files changed, 0 insertions, 0 deletions