On Fri 30-07-10 12:03:06, Wu Fengguang wrote:

On Fri, Jul 30, 2010 at 12:20:27AM +0800, Jan Kara wrote:

quoted

On Thu 29-07-10 19:51:44, Wu Fengguang wrote:

quoted

The periodic/background writeback can run forever. So when any
sync work is enqueued, increase bdi->sync_works to notify the
active non-sync works to exit. Non-sync works queued after sync
works won't be affected.

  Hmm, wouldn't it be simpler logic to just make for_kupdate and
for_background work always yield when there's some other work to do (as
they are livelockable from the definition of the target they have) and
make sure any other work isn't livelockable?

Good idea!

quoted

The only downside is that
non-livelockable work cannot be "fair" in the sense that we cannot switch
inodes after writing MAX_WRITEBACK_PAGES.

Cannot switch indoes _before_ finish with the current
MAX_WRITEBACK_PAGES batch? 

  Well, even after writing all those MAX_WRITEBACK_PAGES. Because what you
want to do in a non-livelockable work is: take inode, write it, never look at
it again for this work. Because if you later return to the inode, it can
have newer dirty pages and thus you cannot really avoid livelock. Of
course, this all assumes .nr_to_write isn't set to something small. That
avoids the livelock as well.

quoted

  I even had a patch for this but it's already outdated by now. But I
can refresh it if we decide this is the way to go.

I'm very interested in your old patch, would you post it? Let's see
which one is easier to work with :)

  OK, attached is the patch. I've rebased it against 2.6.35.

									Honza
-- 
Jan Kara [off-list ref]
SUSE Labs, CR