From: Wu Fengguang <fengguang.wu@intel.com>
To: Chris Mason <chris.mason@oracle.com>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] btrfs: lower the dirty balance poll interval
Date: Tue, 22 Nov 2011 10:21:57 +0800 [thread overview]
Message-ID: <20111122022157.GB20982@localhost> (raw)
In-Reply-To: <20111121203614.GE28259@shiny>
On Tue, Nov 22, 2011 at 04:36:14AM +0800, Chris Mason wrote:
> On Thu, Nov 17, 2011 at 08:24:03PM +0800, Wu Fengguang wrote:
> > Tests show that the original large intervals can easily make the dirty
> > limit exceeded on 100 concurrent dd's. So adapt to as large as the
> > next check point selected by the dirty throttling algorithm.
>
> Thanks Wu, were you planning on pushing this through your tree or should
> I take it?
Will you take it please?
Thanks,
Fengguang
prev parent reply other threads:[~2011-11-22 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 12:24 [PATCH] btrfs: lower the dirty balance poll interval Wu Fengguang
2011-11-21 20:36 ` Chris Mason
2011-11-22 2:21 ` Wu Fengguang [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=20111122022157.GB20982@localhost \
--to=fengguang.wu@intel.com \
--cc=chris.mason@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).