On Fri, Mar 25, 2011 at 11:24:58PM +0100, Jan Kara wrote: > So I think we could stop doing writeback when we have done the transition > of pages from Dirty to Writeback state. We should only make sure someone > kicks the background writeback again when there are enough unstable pages > to be worth a commit. This tends to happen from balance_dirty_pages() or > in the worst case when flusher thread awakes to check for old inodes to > flush. But we can also kick the flusher thread from NFS when we transition > enough pages which would seem rather robust to me. I'll try to write a > patch in this direction. I think making the background writeback commits triggered by NFS write completion is a good way to proceed. A write request completion gives us a guaranteed context to determine if we need to issue a commit or not and should mostly avoid the need for polling or some external event to trigger a threshold check. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
