mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [PATCH 0/2] ext3 data=guarded
@ 2009-04-14 20:57 Chris Mason
  2009-04-14 20:59 ` [PATCH 1/2] Add block_write_full_page_endio for passing endio handler Chris Mason
  2009-04-14 21:00 ` [PATCH 2/2] ext3: add data=guarded mode Chris Mason
  0 siblings, 2 replies; 3+ messages in thread
From: Chris Mason @ 2009-04-14 20:57 UTC (permalink / raw)
  To: Jan Kara, Linus Torvalds, Theodore Ts'o,
	Linux Kernel Developers List, Ext4 Developers List

Hello everyone,

Here is the ext3 data=guarded code again, this time it has passed some
basic tests.  It should safely leave non data=guarded mounts alone and
only be dangerous when the new code is turned on (I hope).

On the performance side, it runs the same as data=writeback, except when
you're making files with holes where it runs the same as data=ordered.

There's definitely more CPU time involved with tracking the data=guarded
buffer heads and updating i_size when the IO is over, but at least on my
5 drive array that doesn't show up.

For the fsync + background streaming write workload, data=guarded does
fsync's in 0.8s, just like data=writeback.  data=ordered on the same
test was doing between 5 and 30s per fsync, so it seems I've fixed that
part at least.

The next step is much more testing (blocksize != pagesize among others)
and much more review.  But, I'm hoping for some feedback first on if
this is a direction we want to take the ext3 code.

The diffstat looks scary, but lots of the changes are comments...

-chris



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-04-14 21:02 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-04-14 20:57 [PATCH 0/2] ext3 data=guarded Chris Mason
2009-04-14 20:59 ` [PATCH 1/2] Add block_write_full_page_endio for passing endio handler Chris Mason
2009-04-14 21:00 ` [PATCH 2/2] ext3: add data=guarded mode Chris Mason

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®