lkml.org 
[lkml]   [2011]   [May]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 06/18] writeback: sync expired inodes first in background writeback
On Tue 24-05-11 13:14:17, Wu Fengguang wrote:
> A background flush work may run for ever. So it's reasonable for it to
> mimic the kupdate behavior of syncing old/expired inodes first.
>
> At each queue_io() time, first try enqueuing only newly expired inodes.
> If there are zero expired inodes to work with, then relax the rule and
> enqueue all dirty inodes.
Fengguang, I've been thinking about this change again (since the code is
now easier to read - good work! - and so I realized some new consequences)
and I was wondering: Assume there is one continuously redirtied file and
untar starts in parallel. With the new logic, background writeback will
never consider inodes that are not expired in this situation (we never
switch to "all dirty inodes" phase - or even if we switched, we would just
queue all inodes and then return back to queueing only expired inodes). So
the net effect is that for 30 seconds we will be only continuously writing
pages of the continuously dirtied file instead of (possibly older) pages of
other files that are written. Is this really desirable? Wasn't the old
behavior simpler and not worse than the new one?

Honza

> --- linux-next.orig/fs/fs-writeback.c 2011-05-24 11:17:18.000000000 +0800
> +++ linux-next/fs/fs-writeback.c 2011-05-24 11:17:18.000000000 +0800
> @@ -718,7 +718,7 @@ static long wb_writeback(struct bdi_writ
> if (work->for_background && !over_bground_thresh())
> break;
>
> - if (work->for_kupdate) {
> + if (work->for_kupdate || work->for_background) {
> oldest_jif = jiffies -
> msecs_to_jiffies(dirty_expire_interval * 10);
> wbc.older_than_this = &oldest_jif;
> @@ -729,6 +729,7 @@ static long wb_writeback(struct bdi_writ
> wbc.pages_skipped = 0;
> wbc.inodes_cleaned = 0;
>
> +retry:
> trace_wbc_writeback_start(&wbc, wb->bdi);
> if (work->sb)
> __writeback_inodes_sb(work->sb, wb, &wbc);
> @@ -752,6 +753,19 @@ static long wb_writeback(struct bdi_writ
> if (wbc.inodes_cleaned)
> continue;
> /*
> + * background writeback will start with expired inodes, and
> + * if none is found, fallback to all inodes. This order helps
> + * reduce the number of dirty pages reaching the end of LRU
> + * lists and cause trouble to the page reclaim.
> + */
> + if (work->for_background &&
> + wbc.older_than_this &&
> + list_empty(&wb->b_io) &&
> + list_empty(&wb->b_more_io)) {
> + wbc.older_than_this = NULL;
> + goto retry;
> + }
> + /*
> * No more inodes for IO, bail
> */
> if (!wbc.more_io)
>
>
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR


\
 
 \ /
  Last update: 2011-05-24 17:55    [from the cache]
©2003-2011 Jasper Spaans