linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 0/4 RESEND] writeback: Dirty list handling changes
@ 2014-05-15 15:41 Jan Kara
  2014-05-15 15:41 ` [PATCH 1/4] writeback: Get rid of superblock pinning Jan Kara
                   ` (4 more replies)
  0 siblings, 5 replies; 12+ messages in thread
From: Jan Kara @ 2014-05-15 15:41 UTC (permalink / raw)
  To: linux-fsdevel; +Cc: Wu Fengguang, Andrew Morton, Jan Kara

  Hello,

  so I was recently thinking about how writeback code shuffles inodes between
lists and also how redirty_tail() clobbers dirtied_when timestamp (which broke
my sync(2) optimization). This patch series came out of that. Patch 1 is a
clear win and just needs an independent review that I didn't forget about
something. Patch 3 changes writeback list handling - IMHO it makes the logic
somewhat more straightforward as we don't have to bother shuffling inodes
between lists and we also don't need to clobber dirtied_when timestamp.
But opinions may differ...

Patches passed xfstests run and I did some basic writeback tests using tiobench
and some artifical sync livelock tests to verify nothing regressed. So I'd
be happy if people could have a look.

								Honza

^ permalink raw reply	[flat|nested] 12+ messages in thread
* [PATCH 0/4 RFC] writeback: Dirty list handling changes
@ 2014-03-20 14:30 Jan Kara
  2014-03-20 14:30 ` [PATCH 4/4] writeback: Remove pages_skipped from writeback_control Jan Kara
  0 siblings, 1 reply; 12+ messages in thread
From: Jan Kara @ 2014-03-20 14:30 UTC (permalink / raw)
  To: linux-fsdevel; +Cc: Wu Fengguang, Andrew Morton, dchinner, Jan Kara

  Hello,

  so I was recently thinking about how writeback code shuffles inodes between
lists and also how redirty_tail() clobbers dirtied_when timestamp (which broke
my sync(2) optimization). This patch series came out of that. Patch 1 is a
clear win and just needs an independent review that I didn't forget about
something. Patch 3 changes writeback list handling - IMHO it makes the logic
somewhat more straightforward as we don't have to bother shuffling inodes
between lists and we also don't need to clobber dirtied_when timestamp.
But opinions may differ...

Patches passed xfstests run so they should be reasonably sound but I also
want to do some targetted tests for sync livelocks, busylocks, etc. before
patches get merged. But before spending too much time with that I wanted to
check what other people think about it.

								Honza

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

end of thread, other threads:[~2014-05-19 16:47 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-05-15 15:41 [PATCH 0/4 RESEND] writeback: Dirty list handling changes Jan Kara
2014-05-15 15:41 ` [PATCH 1/4] writeback: Get rid of superblock pinning Jan Kara
2014-05-15 15:41 ` [PATCH 2/4] writeback: Move removal from writeback list in evict() Jan Kara
2014-05-15 15:41 ` [PATCH 3/4] writeback: Replace several writeback lists with inode tagging Jan Kara
2014-05-15 15:41 ` [PATCH 4/4] writeback: Remove pages_skipped from writeback_control Jan Kara
2014-05-15 23:05   ` Dave Chinner
2014-05-15 23:55 ` [PATCH 0/4 RESEND] writeback: Dirty list handling changes Dave Chinner
2014-05-16  0:47   ` Dave Chinner
2014-05-16  9:27     ` Christoph Hellwig
2014-05-16 22:42       ` Dave Chinner
2014-05-19 16:47     ` Jan Kara
  -- strict thread matches above, loose matches on Subject: below --
2014-03-20 14:30 [PATCH 0/4 RFC] " Jan Kara
2014-03-20 14:30 ` [PATCH 4/4] writeback: Remove pages_skipped from writeback_control Jan Kara

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).