From: Chris Mason <chris.mason@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jan Kara <jack@suse.cz>, Wu Fengguang <fengguang.wu@intel.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 1/2] writeback: Improve busyloop prevention
Date: Fri, 14 Oct 2011 15:31:13 -0400 [thread overview]
Message-ID: <1318620308-sup-2416@shiny> (raw)
In-Reply-To: <20111014071802.GB25687@infradead.org>
Excerpts from Christoph Hellwig's message of 2011-10-14 03:18:02 -0400:
> What btrfs does for the btree inode is insane, and I'm pretty sure I
> already complained about it. It really needs to stop registering that
> inode with the writeback code and just driver it manually. Same as
> other filesystems do for their "micro-managed" metadata.
>
So I think you probably don't like the inode and the part where we
actively decide not to writeback when there isn't much dirty.
Yes, it would be different if btrfs had its own LRU for the btrees, and
if it maintained them such that the LRU understood it was better to kick
out leaves than roots.
I've really wanted to play with this for a while.
-chris
prev parent reply other threads:[~2011-10-14 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1318453043-32057-1-git-send-email-jack@suse.cz>
[not found] ` <1318453043-32057-2-git-send-email-jack@suse.cz>
[not found] ` <20111013142638.GB6938@localhost>
[not found] ` <20111013201354.GC27363@quack.suse.cz>
2011-10-14 7:18 ` [PATCH 1/2] writeback: Improve busyloop prevention Christoph Hellwig
2011-10-14 19:31 ` Chris Mason [this message]
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=1318620308-sup-2416@shiny \
--to=chris.mason@oracle.com \
--cc=david@fromorbit.com \
--cc=fengguang.wu@intel.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--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