From: Wu Fengguang <fengguang.wu@intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux 3.1 issue: bdi dirty threshold goes mad
Date: Mon, 31 Oct 2011 16:33:13 +0800 [thread overview]
Message-ID: <20111031083313.GA12754@localhost> (raw)
In-Reply-To: <20111027225822.GA31990@localhost>
On Fri, Oct 28, 2011 at 06:58:22AM +0800, Wu Fengguang wrote:
> Hi,
>
> FYI, I find bdi dirty threshold madness in the newly released v3.1
> according to the gray lines in the attached graphs, which are for
> these test cases:
>
> 3G-UKEY-HDD/ext4-1dd-4k-8p-2948M-20:10-3.1.0-vanilla+
> 3G-UKEY-HDD/xfs-10dd-4k-8p-2948M-20:10-3.1.0-vanilla+
> 3G-UKEY-HDD/xfs-1dd-4k-8p-2948M-20:10-3.1.0-vanilla+
>
> It's basically doing concurrent dd's to a USB key and a hard disk.
>
> Don't know what's going wrong, but at least should be bisectable..
It seems to depend on kernel builds: the problem disappears in the
newly compiled kernels. This makes it pretty hard to catch the root
cause...
Thanks,
Fengguang
parent reply other threads:[~2011-10-31 8:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20111027225822.GA31990@localhost>]
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=20111031083313.GA12754@localhost \
--to=fengguang.wu@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=jack@suse.cz \
--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).