https://bugzilla.kernel.org/show_bug.cgi?id=14830





--- Comment #31 from Jan Kara <jack@suse.cz>  2010-04-07 09:33:00 ---
(In reply to comment #29)
quoted text
> I'm not familiar enough with all the new writeback code; does this mean that a
> sync will return as soon as any new IO is queued post-sync?  That seems odd if
> so - but maybe I misunderstand.
  No. The patch means that writeback thread stops doing pdflush-style writeback
when it sees new work queued - work does not mean IO. It means that someone
asks writeback thread to do some kind of writeout... Now I'm still not sure my
patch is the right approach to the problem but I just wanted to checkout
whether it
at least solves the problem of this particular workload.

  If you still see the problem (only less often) even with ext3, then we
probably have also some other work that is livelockable and thus we never get
to work submitted by sync(1). I guess I'll have to find a machine with enough
disks and memory to try this out...

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html