From: Jan Kara <jack@suse.cz>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Mel Gorman <mel@csn.ul.ie>, Rik van Riel <riel@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Minchan Kim <minchan.kim@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/4] writeback: integrated background work
Date: Tue, 14 Sep 2010 14:45:55 +0200 [thread overview]
Message-ID: <20100914124555.GB4874@quack.suse.cz> (raw)
In-Reply-To: <20100913130149.849935145@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
On Mon 13-09-10 20:31:11, Wu Fengguang wrote:
> Check background work whenever the flusher thread wakes up. The page
> reclaim code may lower the soft dirty limit immediately before sending
> some work to the flusher thread.
>
> This is also the prerequisite of next patch.
I have a patch doing something functionally rather similar but it also
cleans up the code which isn't necessary after this patch. So could you
maybe consider using that one?
BTW: What has happened with your patch which started writing back old
inodes?
Honza
>
> Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> ---
> fs/fs-writeback.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> --- linux-next.orig/fs/fs-writeback.c 2010-09-13 19:41:21.000000000 +0800
> +++ linux-next/fs/fs-writeback.c 2010-09-13 19:49:11.000000000 +0800
> @@ -716,6 +716,23 @@ get_next_work_item(struct backing_dev_in
> return work;
> }
>
> +static long wb_check_background_flush(struct bdi_writeback *wb)
> +{
> + if (over_bground_thresh()) {
> +
> + struct wb_writeback_work work = {
> + .nr_pages = LONG_MAX,
> + .sync_mode = WB_SYNC_NONE,
> + .for_background = 1,
> + .range_cyclic = 1,
> + };
> +
> + return wb_writeback(wb, &work);
> + }
> +
> + return 0;
> +}
> +
> static long wb_check_old_data_flush(struct bdi_writeback *wb)
> {
> unsigned long expired;
> @@ -787,6 +804,7 @@ long wb_do_writeback(struct bdi_writebac
> * Check for periodic writeback, kupdated() style
> */
> wrote += wb_check_old_data_flush(wb);
> + wrote += wb_check_background_flush(wb);
> clear_bit(BDI_writeback_running, &wb->bdi->state);
>
> return wrote;
>
>
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
[-- Attachment #2: 0001-mm-Check-whether-background-writeback-is-needed-afte.patch --]
[-- Type: text/x-patch, Size: 0 bytes --]
next prev parent reply other threads:[~2010-09-14 12:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 12:31 [PATCH 0/4] [RFC] transfer vmscan pageout works to the flusher thread Wu Fengguang
2010-09-13 12:31 ` [PATCH 1/4] writeback: integrated background work Wu Fengguang
2010-09-13 22:46 ` Minchan Kim
2010-09-14 0:53 ` Wu Fengguang
2010-09-14 12:45 ` Jan Kara [this message]
2010-09-13 12:31 ` [PATCH 2/4] writeback: quit background/periodic work when other works are enqueued Wu Fengguang
2010-09-14 12:40 ` Jan Kara
2010-11-01 12:07 ` Wu Fengguang
2010-11-01 15:08 ` Jan Kara
2010-11-01 15:13 ` Jan Kara
2010-11-01 12:14 ` [PATCH 1/2] writeback: integrated background writeback work Wu Fengguang
2010-11-01 12:22 ` [PATCH 2/2] writeback: stop background/kupdate works from livelocking other works Wu Fengguang
2010-11-01 15:22 ` Christoph Hellwig
2010-11-02 1:57 ` Minchan Kim
2010-11-05 12:15 ` Johannes Weiner
2010-11-01 15:21 ` [PATCH 1/2] writeback: integrated background writeback work Christoph Hellwig
2010-11-01 20:37 ` Wu Fengguang
2010-11-01 20:39 ` [PATCH 1/2 v2] " Wu Fengguang
2010-11-02 1:55 ` Minchan Kim
2010-11-05 12:01 ` Johannes Weiner
2010-09-13 12:31 ` [PATCH 3/4] writeback: introduce bdi_start_inode_writeback() Wu Fengguang
2010-09-14 13:36 ` Jan Kara
2010-11-01 12:35 ` Wu Fengguang
2010-09-13 12:31 ` [PATCH 4/4] vmscan: transfer async file writeback to the flusher 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=20100914124555.GB4874@quack.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.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;
as well as URLs for NNTP newsgroup(s).