From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org,
Wu Fengguang <fengguang.wu@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/4 RESEND] writeback: Dirty list handling changes
Date: Sat, 17 May 2014 08:42:44 +1000 [thread overview]
Message-ID: <20140516224244.GH26353@dastard> (raw)
In-Reply-To: <20140516092720.GA27594@infradead.org>
On Fri, May 16, 2014 at 02:27:20AM -0700, Christoph Hellwig wrote:
> > Seems to me that this problem has been solved elswhere in the
> > kernel, like for tracking of timers to expire on a given jiffie
> > (tvec, tvec_base, timer_lists). Perhaps we should be looking to move
> > to a set of time based lists for efficiently tracking what inodes
> > should be written back at a given background writeback interval
> > rather than trying to keep everything on the one list.
>
> It's also pretty similar to the mru cache we use for filesystems in XFS,
> except that we'd start writeback instead of deleting items. The whole
> bucket scheme there should also help with I/O batching.
*nod*
I thought about that, but then though that an example from a core
subsystem would be better ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-05-16 22:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 15:41 [PATCH 0/4 RESEND] writeback: Dirty list handling changes Jan Kara
2014-05-15 15:41 ` [PATCH 1/4] writeback: Get rid of superblock pinning Jan Kara
2014-05-15 15:41 ` [PATCH 2/4] writeback: Move removal from writeback list in evict() Jan Kara
2014-05-15 15:41 ` [PATCH 3/4] writeback: Replace several writeback lists with inode tagging Jan Kara
2014-05-15 15:41 ` [PATCH 4/4] writeback: Remove pages_skipped from writeback_control Jan Kara
2014-05-15 23:05 ` Dave Chinner
2014-05-15 23:55 ` [PATCH 0/4 RESEND] writeback: Dirty list handling changes Dave Chinner
2014-05-16 0:47 ` Dave Chinner
2014-05-16 9:27 ` Christoph Hellwig
2014-05-16 22:42 ` Dave Chinner [this message]
2014-05-19 16:47 ` Jan Kara
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=20140516224244.GH26353@dastard \
--to=david@fromorbit.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
/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).