From: Jan Kara <jack@suse.cz>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Dave Chinner <david@fromorbit.com>, Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@linux.vnet.ibm.com>, Mel Gorman <mel@csn.ul.ie>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
Itaru Kitayama <kitayama@cl.bb4u.ne.jp>,
Minchan Kim <minchan.kim@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH 3/6] writeback: sync expired inodes first in background writeback
Date: Thu, 21 Apr 2011 18:04:05 +0200 [thread overview]
Message-ID: <20110421160405.GB4476@quack.suse.cz> (raw)
In-Reply-To: <20110421041010.GA18710@localhost>
On Thu 21-04-11 12:10:11, Wu Fengguang wrote:
> > > Still, given wb_writeback() is the only caller of both
> > > __writeback_inodes_sb and writeback_inodes_wb(), I'm wondering if
> > > moving the queue_io calls up into wb_writeback() would clean up this
> > > logic somewhat. I think Jan mentioned doing something like this as
> > > well elsewhere in the thread...
> >
> > Unfortunately they call queue_io() inside the lock..
>
> OK, let's try moving up the lock too. Do you like this change? :)
>
> Thanks,
> Fengguang
> ---
> fs/fs-writeback.c | 22 ++++++----------------
> mm/backing-dev.c | 4 ++++
> 2 files changed, 10 insertions(+), 16 deletions(-)
>
> --- linux-next.orig/fs/fs-writeback.c 2011-04-21 12:04:02.000000000 +0800
> +++ linux-next/fs/fs-writeback.c 2011-04-21 12:05:54.000000000 +0800
> @@ -591,7 +591,6 @@ void writeback_inodes_wb(struct bdi_writ
>
> if (!wbc->wb_start)
> wbc->wb_start = jiffies; /* livelock avoidance */
> - spin_lock(&inode_wb_list_lock);
>
> if (list_empty(&wb->b_io))
> queue_io(wb, wbc);
> @@ -610,22 +609,9 @@ void writeback_inodes_wb(struct bdi_writ
> if (ret)
> break;
> }
> - spin_unlock(&inode_wb_list_lock);
> /* Leave any unwritten inodes on b_io */
> }
>
> -static void __writeback_inodes_sb(struct super_block *sb,
> - struct bdi_writeback *wb, struct writeback_control *wbc)
> -{
> - WARN_ON(!rwsem_is_locked(&sb->s_umount));
> -
> - spin_lock(&inode_wb_list_lock);
> - if (list_empty(&wb->b_io))
> - queue_io(wb, wbc);
> - writeback_sb_inodes(sb, wb, wbc, true);
> - spin_unlock(&inode_wb_list_lock);
> -}
> -
> static inline bool over_bground_thresh(void)
> {
> unsigned long background_thresh, dirty_thresh;
> @@ -652,7 +638,7 @@ static unsigned long writeback_chunk_siz
> * The intended call sequence for WB_SYNC_ALL writeback is:
> *
> * wb_writeback()
> - * __writeback_inodes_sb() <== called only once
> + * writeback_sb_inodes() <== called only once
> * write_cache_pages() <== called once for each inode
> * (quickly) tag currently dirty pages
> * (maybe slowly) sync all tagged pages
> @@ -742,10 +728,14 @@ static long wb_writeback(struct bdi_writ
>
> retry:
> trace_wbc_writeback_start(&wbc, wb->bdi);
> + spin_lock(&inode_wb_list_lock);
> + if (list_empty(&wb->b_io))
> + queue_io(wb, wbc);
> if (work->sb)
> - __writeback_inodes_sb(work->sb, wb, &wbc);
> + writeback_sb_inodes(work->sb, wb, &wbc, true);
> else
> writeback_inodes_wb(wb, &wbc);
> + spin_unlock(&inode_wb_list_lock);
> trace_wbc_writeback_written(&wbc, wb->bdi);
>
> bdi_update_write_bandwidth(wb->bdi, wbc.wb_start);
> --- linux-next.orig/mm/backing-dev.c 2011-04-21 12:06:02.000000000 +0800
> +++ linux-next/mm/backing-dev.c 2011-04-21 12:06:31.000000000 +0800
> @@ -268,7 +268,11 @@ static void bdi_flush_io(struct backing_
> .nr_to_write = 1024,
> };
>
> + spin_lock(&inode_wb_list_lock);
> + if (list_empty(&wb->b_io))
> + queue_io(wb, wbc);
> writeback_inodes_wb(&bdi->wb, &wbc);
> + spin_unlock(&inode_wb_list_lock);
> }
Three notes here:
1) You are missing the call to writeback_inodes_wb() in
balance_dirty_pages() (the patch should really work for vanilla kernels).
2) The intention of both bdi_flush_io() and balance_dirty_pages() is to
write .nr_to_write pages. So they should either do queue_io()
unconditionally (I kind of like that for simplicity) or they should requeue
once if they have not written enough - otherwise it could happen that they
are called just at the moment when b_io contains a single inode with a few
dirty pages and they end up doing almost nothing.
3) I guess your patch does not compile because queue_io() is static ;).
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-04-21 16:04 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 3:00 [PATCH 0/6] writeback: moving expire targets for background/kupdate works Wu Fengguang
2011-04-19 3:00 ` [PATCH 1/6] writeback: pass writeback_control down to move_expired_inodes() Wu Fengguang
2011-04-19 3:00 ` [PATCH 2/6] writeback: the kupdate expire timestamp should be a moving target Wu Fengguang
2011-04-19 7:02 ` Dave Chinner
2011-04-19 7:20 ` Wu Fengguang
2011-04-19 9:31 ` Jan Kara
2011-04-19 3:00 ` [PATCH 3/6] writeback: sync expired inodes first in background writeback Wu Fengguang
2011-04-19 7:35 ` Dave Chinner
2011-04-19 9:57 ` Jan Kara
2011-04-19 12:56 ` Wu Fengguang
2011-04-19 13:46 ` Wu Fengguang
2011-04-20 1:21 ` Dave Chinner
2011-04-20 2:53 ` Wu Fengguang
2011-04-21 0:45 ` Dave Chinner
2011-04-21 2:06 ` Wu Fengguang
2011-04-21 3:01 ` Dave Chinner
2011-04-21 3:59 ` Wu Fengguang
2011-04-21 4:10 ` Wu Fengguang
2011-04-21 4:36 ` Christoph Hellwig
2011-04-21 6:36 ` Dave Chinner
2011-04-21 16:04 ` Jan Kara [this message]
2011-04-22 2:24 ` Wu Fengguang
2011-04-22 21:12 ` Jan Kara
2011-04-26 5:37 ` Wu Fengguang
2011-04-26 14:30 ` Jan Kara
2011-04-20 7:38 ` Wu Fengguang
2011-04-21 1:01 ` Dave Chinner
2011-04-21 1:47 ` Wu Fengguang
2011-04-19 3:00 ` [PATCH 4/6] writeback: introduce writeback_control.inodes_cleaned Wu Fengguang
2011-04-19 9:47 ` Jan Kara
2011-04-19 3:00 ` [PATCH 5/6] writeback: try more writeback as long as something was written Wu Fengguang
2011-04-19 10:20 ` Jan Kara
2011-04-19 11:16 ` Wu Fengguang
2011-04-19 21:10 ` Jan Kara
2011-04-20 7:50 ` Wu Fengguang
2011-04-20 15:22 ` Jan Kara
2011-04-21 3:33 ` Wu Fengguang
2011-04-21 4:39 ` Christoph Hellwig
2011-04-21 6:05 ` Wu Fengguang
2011-04-21 16:41 ` Jan Kara
2011-04-22 2:32 ` Wu Fengguang
2011-04-22 21:23 ` Jan Kara
2011-04-21 7:09 ` Dave Chinner
2011-04-21 7:14 ` Christoph Hellwig
2011-04-21 7:52 ` Dave Chinner
2011-04-21 8:00 ` Christoph Hellwig
2011-04-19 3:00 ` [PATCH 6/6] NFS: return -EAGAIN when skipped commit in nfs_commit_unstable_pages() Wu Fengguang
2011-04-19 3:29 ` Trond Myklebust
2011-04-19 3:55 ` Wu Fengguang
2011-04-21 4:40 ` Christoph Hellwig
2011-04-19 6:38 ` [PATCH 0/6] writeback: moving expire targets for background/kupdate works Dave Chinner
2011-04-19 8:02 ` Wu Fengguang
2011-04-21 4:34 ` Christoph Hellwig
2011-04-21 5:50 ` Wu Fengguang
2011-04-21 5:56 ` Christoph Hellwig
2011-04-21 6:07 ` Wu Fengguang
2011-04-21 7:17 ` Christoph Hellwig
2011-04-21 10:15 ` Wu Fengguang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110421160405.GB4476@quack.suse.cz \
--to=jack@suse.cz \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=fengguang.wu@intel.com \
--cc=kitayama@cl.bb4u.ne.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mel@linux.vnet.ibm.com \
--cc=minchan.kim@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox