From: Arjan van de Ven <arjan@infradead.org>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
"Li, Shaohua" <shaohua.li@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Chris Mason <chris.mason@oracle.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Jan Kara <jack@suse.cz>
Subject: Re: [RFC] page-writeback: move indoes from one superblock together
Date: Thu, 24 Sep 2009 15:52:17 +0200 [thread overview]
Message-ID: <20090924155217.5ad0de4b@infradead.org> (raw)
In-Reply-To: <20090924134625.GA2507@localhost>
On Thu, 24 Sep 2009 21:46:25 +0800
Wu Fengguang <fengguang.wu@intel.com> wrote:
>
> Note that dirty_time may not be unique, so need some workaround. And
> the resulted rbtree implementation may not be more efficient than
> several list traversals even for a very large list (as long as
> superblocks numbers are low).
>
> The good side is, once sb+dirty_time rbtree is implemented, it should
> be trivial to switch the key to sb+inode_number (also may not be
> unique), and to do location ordered writeback ;)
would you want to sort by dirty time, or by inode number?
(assuming inode number is loosely related to location on disk)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-09-24 13:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1253775260.10618.10.camel@sli10-desk.sh.intel.com>
2009-09-24 7:14 ` [RFC] page-writeback: move indoes from one superblock together Wu Fengguang
2009-09-24 7:29 ` Arjan van de Ven
2009-09-24 7:36 ` Wu Fengguang
2009-09-24 7:44 ` Shaohua Li
2009-09-24 13:17 ` Jens Axboe
2009-09-24 13:29 ` Wu Fengguang
2009-09-24 10:01 ` Wu Fengguang
2009-09-24 12:35 ` Jens Axboe
2009-09-24 13:22 ` Wu Fengguang
2009-09-24 13:29 ` Jens Axboe
2009-09-24 13:46 ` Wu Fengguang
2009-09-24 13:52 ` Arjan van de Ven [this message]
2009-09-24 14:09 ` Wu Fengguang
2009-09-25 4:16 ` Dave Chinner
2009-09-25 5:09 ` 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=20090924155217.5ad0de4b@infradead.org \
--to=arjan@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.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).