|| ||"Darrick J. Wong" <firstname.lastname@example.org> |
|| ||email@example.com, firstname.lastname@example.org, email@example.com,
"Darrick J. Wong" <firstname.lastname@example.org>, email@example.com,
firstname.lastname@example.org, email@example.com, firstname.lastname@example.org |
|| ||[PATCH v2.3 0/3] mm/fs: Implement faster stable page writes on
|| ||Thu, 13 Dec 2012 00:07:40 -0800|
|| ||email@example.com, firstname.lastname@example.org, email@example.com,
Zheng Liu <firstname.lastname@example.org>,
|| ||Article, Thread
This patchset ("stable page writes, part 2") makes some key modifications to
the original 'stable page writes' patchset. First, it provides creators
(devices and filesystems) of a backing_dev_info a flag that declares whether or
not it is necessary to ensure that page contents cannot change during writeout.
It is no longer assumed that this is true of all devices (which was never true
anyway). Second, the flag is used to relaxed the wait_on_page_writeback calls
so that wait only occurs if the device needs it. Third, it fixes up the
remaining disk-backed filesystems to use this improved conditional-wait logic
to provide stable page writes on those filesystems.
It is hoped that (for people not using checksumming devices, anyway) this
patchset will give back unnecessary performance decreases since the original
stable page write patchset went into 3.0. Sorry about not fixing it sooner.
Complaints were registered by several people about the long write latencies
introduced by the original stable page write patchset. Generally speaking, the
kernel ought to allocate as little extra memory as possible to facilitate
writeout, but for people who simply cannot wait, a second page stability
strategy is (re)introduced: snapshotting page contents. The waiting behavior
is still the default strategy; to enable page snapshotting, a superblock flag
(MS_SNAP_STABLE) must be set. This flag is primary used to bandaid^Henable
stable page writeout on ext3, but a mount options is provided for impatient
Given that there are already a few storage devices and network FSes that have
rolled their own page stability wait/page snapshot code, it would be nice to
move towards consolidating all of these. It seems possible that iscsi and
raid5 may wish to use the new stable page write support to enable zero-copy
In the future, it would be useful to develop a heuristic to select a strategy
automatically rather than leaving it up to manual control.
This patchset has been lightly tested on 3.7.0 on x64 with ext3, ext4, and xfs.
 The alternative fixes to ext3 include fixing the locking order and page bit
handling like we did for ext4 (but then why not just use ext4?), or setting
PG_writeback so early that ext3 becomes extremely slow. I tried that, but the
number of write()s I could initiate dropped by nearly an order of magnitude.
That was a bit much even for the author of the stable page series! :)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/