From: Wu Fengguang <fengguang.wu@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.cz>, Mel Gorman <mel@linux.vnet.ibm.com>,
Mel Gorman <mel@csn.ul.ie>, Dave Chinner <david@fromorbit.com>,
Itaru Kitayama <kitayama@cl.bb4u.ne.jp>,
Minchan Kim <minchan.kim@gmail.com>,
Linux Memory Management List <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/6] writeback: introduce writeback_control.inodes_cleaned
Date: Wed, 4 May 2011 19:32:11 +0800 [thread overview]
Message-ID: <20110504113211.GA5853@localhost> (raw)
In-Reply-To: <20110504111647.GA19261@infradead.org>
On Wed, May 04, 2011 at 07:16:47PM +0800, Christoph Hellwig wrote:
> On Wed, May 04, 2011 at 07:11:30PM +0800, Wu Fengguang wrote:
> > On Wed, May 04, 2011 at 07:05:00PM +0800, Christoph Hellwig wrote:
> > > Same here - this has nothing to do with actual page writeback and really
> > > should stay internal to fs/fs-writeback.c
> >
> > OK, I'll check how to constrain writeback_control to the minimal scope.
>
> The basic idea would be to pass the struct wb_writeback_work all the
> way down to writeback_sb_inodes, and initialize the struct writeback_control
> there.
OK.
> This requires adding a few more fields like more_io and
We can in fact just kill more_io and test list_empty(b_more_io)
instead.
> older_than_this to struct wb_writeback_work, and redoing a lot of the
> tracing,
Yeah, older_than_this must still be set in wb_writeback().
The two trace points could be removed for now.
> but it immediately clean things up, e.g. suddently
> wbc.nr_to_write vs work->nr_pages starts to make sense, and instead
> of saving and restoring pages_skipped in writeback_sb_inodes it can
> always start with a clean zero value.
That's right.
Thanks,
Fengguang
WARNING: multiple messages have this Message-ID (diff)
From: Wu Fengguang <fengguang.wu@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.cz>, Mel Gorman <mel@linux.vnet.ibm.com>,
Mel Gorman <mel@csn.ul.ie>, Dave Chinner <david@fromorbit.com>,
Itaru Kitayama <kitayama@cl.bb4u.ne.jp>,
Minchan Kim <minchan.kim@gmail.com>,
Linux Memory Management List <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/6] writeback: introduce writeback_control.inodes_cleaned
Date: Wed, 4 May 2011 19:32:11 +0800 [thread overview]
Message-ID: <20110504113211.GA5853@localhost> (raw)
In-Reply-To: <20110504111647.GA19261@infradead.org>
On Wed, May 04, 2011 at 07:16:47PM +0800, Christoph Hellwig wrote:
> On Wed, May 04, 2011 at 07:11:30PM +0800, Wu Fengguang wrote:
> > On Wed, May 04, 2011 at 07:05:00PM +0800, Christoph Hellwig wrote:
> > > Same here - this has nothing to do with actual page writeback and really
> > > should stay internal to fs/fs-writeback.c
> >
> > OK, I'll check how to constrain writeback_control to the minimal scope.
>
> The basic idea would be to pass the struct wb_writeback_work all the
> way down to writeback_sb_inodes, and initialize the struct writeback_control
> there.
OK.
> This requires adding a few more fields like more_io and
We can in fact just kill more_io and test list_empty(b_more_io)
instead.
> older_than_this to struct wb_writeback_work, and redoing a lot of the
> tracing,
Yeah, older_than_this must still be set in wb_writeback().
The two trace points could be removed for now.
> but it immediately clean things up, e.g. suddently
> wbc.nr_to_write vs work->nr_pages starts to make sense, and instead
> of saving and restoring pages_skipped in writeback_sb_inodes it can
> always start with a clean zero value.
That's right.
Thanks,
Fengguang
--
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-05-04 11:32 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 8:03 [PATCH 0/6] writeback: moving expire targets for background/kupdate works v2 Wu Fengguang
2011-04-20 8:03 ` Wu Fengguang
2011-04-20 8:03 ` [PATCH 1/6] writeback: pass writeback_control down to move_expired_inodes() Wu Fengguang
2011-04-20 8:03 ` Wu Fengguang
2011-05-04 11:04 ` Christoph Hellwig
2011-05-04 11:04 ` Christoph Hellwig
2011-05-04 11:13 ` Wu Fengguang
2011-05-04 11:13 ` Wu Fengguang
2011-04-20 8:03 ` [PATCH 2/6] writeback: introduce writeback_control.inodes_cleaned Wu Fengguang
2011-04-20 8:03 ` Wu Fengguang
2011-04-20 8:03 ` Wu Fengguang
2011-05-04 11:05 ` Christoph Hellwig
2011-05-04 11:05 ` Christoph Hellwig
2011-05-04 11:11 ` Wu Fengguang
2011-05-04 11:11 ` Wu Fengguang
2011-05-04 11:16 ` Christoph Hellwig
2011-05-04 11:16 ` Christoph Hellwig
2011-05-04 11:32 ` Wu Fengguang [this message]
2011-05-04 11:32 ` Wu Fengguang
2011-04-20 8:03 ` [PATCH 3/6] writeback: try more writeback as long as something was written Wu Fengguang
2011-04-20 8:03 ` Wu Fengguang
2011-04-20 8:03 ` Wu Fengguang
2011-04-20 8:03 ` [PATCH 4/6] writeback: the kupdate expire timestamp should be a moving target Wu Fengguang
2011-04-20 8:03 ` Wu Fengguang
2011-04-20 8:03 ` [PATCH 5/6] writeback: sync expired inodes first in background writeback Wu Fengguang
2011-04-20 8:03 ` Wu Fengguang
2011-04-20 8:03 ` Wu Fengguang
2011-04-20 23:40 ` Andrew Morton
2011-04-20 23:40 ` Andrew Morton
2011-04-20 23:40 ` Andrew Morton
2011-04-21 1:14 ` Wu Fengguang
2011-04-21 1:14 ` Wu Fengguang
2011-04-21 1:21 ` Wu Fengguang
2011-04-21 1:21 ` Wu Fengguang
2011-04-24 3:15 ` Wu Fengguang
2011-04-24 3:15 ` Wu Fengguang
2011-04-26 12:17 ` Jan Kara
2011-04-26 12:17 ` Jan Kara
2011-04-26 13:51 ` Wu Fengguang
2011-04-26 13:51 ` Wu Fengguang
2011-04-26 13:59 ` Wu Fengguang
2011-04-26 13:59 ` Wu Fengguang
2011-04-26 14:05 ` Wu Fengguang
2011-04-26 14:05 ` Wu Fengguang
2011-04-27 11:15 ` Wu Fengguang
2011-04-27 11:15 ` Wu Fengguang
2011-04-20 8:03 ` [PATCH 6/6] writeback: refill b_io iff empty Wu Fengguang
2011-04-20 8:03 ` Wu Fengguang
2011-04-20 8:03 ` Wu Fengguang
2011-05-04 7:39 ` Wu Fengguang
2011-05-05 16:37 ` Jan Kara
2011-05-05 16:37 ` Jan Kara
2011-05-05 16:47 ` Wu Fengguang
2011-05-05 16:47 ` Wu Fengguang
2011-05-06 5:29 ` Wu Fengguang
2011-05-06 5:29 ` Wu Fengguang
2011-05-06 8:42 ` [RFC][PATCH] writeback: limit number of moved inodes in queue_io() Wu Fengguang
2011-05-06 8:42 ` Wu Fengguang
2011-05-06 10:06 ` [RFC][PATCH v2] " Wu Fengguang
2011-05-06 10:06 ` Wu Fengguang
2011-05-06 23:06 ` Dave Chinner
2011-05-06 23:06 ` Dave Chinner
2011-05-06 14:21 ` [PATCH 6/6] writeback: refill b_io iff empty Jan Kara
2011-05-06 14:21 ` Jan Kara
2011-05-10 4:31 ` Wu Fengguang
2011-05-10 4:53 ` Dave Chinner
2011-05-10 4:53 ` Dave Chinner
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=20110504113211.GA5853@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.