From: Rik van Riel <riel@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: Wu Fengguang <fengguang.wu@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>, Mel Gorman <mel@csn.ul.ie>,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 06/17] writeback: sync expired inodes first in background writeback
Date: Mon, 09 May 2011 12:18:19 -0400 [thread overview]
Message-ID: <4DC813CB.2040103@redhat.com> (raw)
In-Reply-To: <20110509160827.GS4122@quack.suse.cz>
On 05/09/2011 12:08 PM, Jan Kara wrote:
> The age of pages in LRU is not necessarily related with the
> i_dirtied_when time stamp so I'm not sure how much this will help after all
Not necessarily, but given that the inactive file list is a
FIFO list, I expect there will be decent correlation.
> but it makes some sense from the data integrity point of view at least. You
> can add:
> Acked-by: Jan Kara<jack@suse.cz>
Good point on the data integrity.
--
All rights reversed
next prev parent reply other threads:[~2011-05-09 16:19 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 3:08 [PATCH 00/17] writeback fixes and cleanups for 2.6.40 Wu Fengguang
2011-05-06 3:08 ` [PATCH 01/17] writeback: introduce wbc.tagged_sync for the WB_SYNC_NONE sync stage Wu Fengguang
2011-05-06 16:08 ` Jan Kara
2011-05-06 3:08 ` [PATCH 02/17] writeback: update dirtied_when for synced inode to prevent livelock Wu Fengguang
2011-05-06 16:33 ` Jan Kara
2011-05-10 2:14 ` Wu Fengguang
2011-05-10 12:05 ` Jan Kara
2011-05-06 3:08 ` [PATCH 03/17] writeback: introduce writeback_control.inodes_cleaned Wu Fengguang
2011-05-06 14:36 ` Jan Kara
2011-05-10 2:23 ` Wu Fengguang
2011-05-10 13:52 ` Jan Kara
2011-05-10 15:00 ` Wu Fengguang
2011-05-06 3:08 ` [PATCH 04/17] writeback: try more writeback as long as something was written Wu Fengguang
2011-05-09 16:05 ` Jan Kara
2011-05-10 2:40 ` Wu Fengguang
2011-05-06 3:08 ` [PATCH 05/17] writeback: the kupdate expire timestamp should be a moving target Wu Fengguang
2011-05-06 3:08 ` [PATCH 06/17] writeback: sync expired inodes first in background writeback Wu Fengguang
2011-05-06 19:02 ` Rik van Riel
2011-05-09 16:08 ` Jan Kara
2011-05-09 16:18 ` Rik van Riel [this message]
2011-05-10 2:45 ` Wu Fengguang
2011-05-06 3:08 ` [PATCH 07/17] writeback: refill b_io iff empty Wu Fengguang
2011-05-06 3:08 ` [PATCH 08/17] writeback: split inode_wb_list_lock into bdi_writeback.list_lock Wu Fengguang
2011-05-06 3:08 ` [PATCH 09/17] writeback: elevate queue_io() into wb_writeback() Wu Fengguang
2011-05-09 16:15 ` Jan Kara
2011-05-06 3:08 ` [PATCH 10/17] writeback: avoid extra sync work at enqueue time Wu Fengguang
2011-05-09 16:16 ` Jan Kara
2011-05-06 3:08 ` [PATCH 11/17] writeback: add bdi_dirty_limit() kernel-doc Wu Fengguang
2011-05-06 3:08 ` [PATCH 12/17] writeback: skip balance_dirty_pages() for in-memory fs Wu Fengguang
2011-05-06 3:08 ` [PATCH 13/17] writeback: remove writeback_control.more_io Wu Fengguang
2011-05-06 3:08 ` [PATCH 14/17] writeback: make writeback_control.nr_to_write straight Wu Fengguang
2011-05-09 16:54 ` Jan Kara
2011-05-10 3:19 ` Wu Fengguang
2011-05-10 13:44 ` Jan Kara
2011-05-11 14:38 ` Wu Fengguang
2011-05-11 14:54 ` Jan Kara
2011-05-06 3:08 ` [PATCH 15/17] writeback: remove .nonblocking and .encountered_congestion Wu Fengguang
2011-05-06 3:08 ` [PATCH 16/17] writeback: trace event writeback_single_inode Wu Fengguang
2011-05-06 4:16 ` [PATCH 16/17] writeback: trace event writeback_single_inode (v2) Wu Fengguang
2011-05-06 3:08 ` [PATCH 17/17] writeback: trace event writeback_queue_io Wu Fengguang
2011-05-06 4:06 ` [PATCH 00/17] writeback fixes and cleanups for 2.6.40 Anca Emanuel
2011-05-06 4:09 ` Wu Fengguang
-- strict thread matches above, loose matches on Subject: below --
2011-05-12 13:57 [PATCH 00/17] writeback fixes and cleanups for 2.6.40 (v2) Wu Fengguang
2011-05-12 13:57 ` [PATCH 06/17] writeback: sync expired inodes first in background writeback Wu Fengguang
2011-05-12 22:55 ` Dave Chinner
2011-05-16 13:00 ` 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=4DC813CB.2040103@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=fengguang.wu@intel.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
/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.