From: Andy Lutomirski <luto@amacapital.net>
To: linux-kernel@vger.kernel.org,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Cc: Dave Chinner <david@fromorbit.com>,
Al Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
Andy Lutomirski <luto@amacapital.net>
Subject: [RFC PATCH 0/4] Rework mtime and ctime updates on mmaped writes
Date: Thu, 20 Dec 2012 15:10:08 -0800 [thread overview]
Message-ID: <cover.1356043686.git.luto@amacapital.net> (raw)
In-Reply-To: <CALCETrUxFHHVPO=EC0jmV9SSKJiOm-mc-xwsd6Ruk3p5nC4fFQ@mail.gmail.com>
Writes via mmap currently update mtime and ctime in ->page_mkwrite.
This is unfortunate from a performance and a correctness point of view.
The file times should be updated after writes, not before (so that every
write eventually results in a fresh timestamp). More importantly
(for me), ->page_mkwrite is called periodically even on mlocked pages,
and some filesystems can sleep in mark_inode_dirty.
This patchset attempts to fix both issues at once. It adds a new
address_space flag AS_CMTIME that is set atomically whenever the system
transfers a pte dirty bit to a struct page backed by the address_space.
This can happen with various locks held and when low on memory.
Later on, whenever syncing an inode (which happens indirectly in msync)
or whenever a vma is torn down, if AS_CMTIME is set, then the file times
are updated. This happens in a context from which (I think) it's safe
to dirty inodes.
One nice property of this approach is that it requires no fs-specific
work. It's actually quite a bit simpler than I expected.
I've tested this, and mtime and ctime are updated on munmap, exit, MS_SYNC,
and fsync after writing via mmap. The times are also updated 30 seconds
after writing, all by themselves :) Lockdep has no complaints.
NB: I am not at all an expert in anything fs or pagecache related. Please
help me find things that may be wrong with these patches.
Andy Lutomirski (4):
mm: Explicitly track when the page dirty bit is transferred from a
pte
mm: Update file times when inodes are written after mmaped writes
Remove file_update_time from all mkwrite paths
ext4: Fix an incorrect comment about i_mutex
fs/9p/vfs_file.c | 3 ---
fs/btrfs/inode.c | 4 +---
fs/buffer.c | 6 ------
fs/ceph/addr.c | 3 ---
fs/ext4/fsync.c | 2 --
fs/ext4/inode.c | 1 -
fs/gfs2/file.c | 3 ---
fs/inode.c | 37 +++++++++++++++++++++++++++++++++++++
fs/nilfs2/file.c | 1 -
fs/sysfs/bin.c | 2 --
include/linux/fs.h | 1 +
include/linux/mm.h | 1 +
include/linux/pagemap.h | 3 +++
mm/filemap.c | 1 -
mm/memory-failure.c | 4 +---
mm/memory.c | 5 +----
mm/mmap.c | 4 ++++
mm/page-writeback.c | 42 ++++++++++++++++++++++++++++++++++++++++--
mm/rmap.c | 9 ++++++---
19 files changed, 95 insertions(+), 37 deletions(-)
--
1.7.11.7
next prev parent reply other threads:[~2012-12-20 23:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 1:10 Are there u32 atomic bitops? (or dealing w/ i_flags) Andy Lutomirski
2012-12-18 1:34 ` Ming Lei
2012-12-18 1:57 ` Al Viro
2012-12-18 2:42 ` Andy Lutomirski
2012-12-18 21:30 ` Dave Chinner
2012-12-18 22:20 ` Andy Lutomirski
2012-12-20 7:03 ` Dave Chinner
2012-12-20 20:05 ` Andy Lutomirski
2012-12-20 23:10 ` Andy Lutomirski [this message]
2012-12-20 23:10 ` [RFC PATCH 1/4] mm: Explicitly track when the page dirty bit is transferred from a pte Andy Lutomirski
2012-12-20 23:10 ` [RFC PATCH 2/4] mm: Update file times when inodes are written after mmaped writes Andy Lutomirski
2012-12-21 0:14 ` Dave Chinner
2012-12-21 0:58 ` Jan Kara
2012-12-21 1:12 ` Dave Chinner
2012-12-21 1:36 ` Jan Kara
2012-12-21 5:36 ` Andy Lutomirski
2012-12-21 10:51 ` Jan Kara
2012-12-21 18:26 ` Andy Lutomirski
2012-12-21 0:34 ` Jan Kara
2012-12-21 5:42 ` Andy Lutomirski
2012-12-21 11:03 ` Jan Kara
2012-12-20 23:10 ` [RFC PATCH 3/4] Remove file_update_time from all mkwrite paths Andy Lutomirski
2012-12-20 23:10 ` [RFC PATCH 4/4] ext4: Fix an incorrect comment about i_mutex Andy Lutomirski
2012-12-20 23:42 ` Jan Kara
2012-12-20 23:36 ` Are there u32 atomic bitops? (or dealing w/ i_flags) Dave Chinner
2012-12-20 23:42 ` Andy Lutomirski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1356043686.git.luto@amacapital.net \
--to=luto@amacapital.net \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).