From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: James Cloos <cloos@jhcloos.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org,
jfs-discussion@lists.sourceforge.net
Subject: Re: [Regression] Filesystem I/O is CPU-bound in rc7 and rc8
Date: Mon, 15 Feb 2010 00:12:25 +0100 [thread overview]
Message-ID: <201002150012.25572.rjw@sisk.pl> (raw)
In-Reply-To: <m3pr48bjfg.fsf@lugabout.jhcloos.org>
On Sunday 14 February 2010, James Cloos wrote:
> Sometime between rc6 and rc7 all filesystem I/O started using 100% CPU,
> usually on the order of 60% sys, 40% user.
>
> I've tried this with each of ext4, jfs and btrfs filesystems. All show
> the same issue.
>
> Using dd(1) to read from the block specials directly works as well and
> as fast as it always has; only reading or writing to mounted filesystems
> is affected.
>
> Box is 32-bit x86, PentiumIII-M; drives are ide using libata.
>
> If the btrfs fs is mounted, the slowdown is enought to trigger the
> hung_task call trace (120s) on the btrfs-transac process.
>
> But the regression is just as apparent when only jfs and ext4 are mounted.
>
> The only filesystems I've found which avoid the regression are tmpfs and
> devtmpfs.
>
> I didn't have time to write up a report when I noticed this in rc7 but
> had to boot back into rc6 for work.
>
> Some of the commits since rc7 looked like they might have addressed this
> regression, but it persists in rc8.
I have created the bug entry at http://bugzilla.kernel.org/show_bug.cgi?id=15306
for your report.
Thanks,
Rafael
next prev parent reply other threads:[~2010-02-14 23:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 3:11 [Regression] Filesystem I/O is CPU-bound in rc7 and rc8 James Cloos
2010-02-14 16:40 ` James Cloos
2010-02-14 23:12 ` Rafael J. Wysocki [this message]
2010-02-15 15:45 ` Chris Mason
2010-02-15 19:27 ` James Cloos
2010-02-17 20:04 ` James Cloos
2010-02-19 21:02 ` Dave Airlie
2010-02-19 21:37 ` James Cloos
2010-02-19 22:03 ` Dave Airlie
2010-02-20 15:59 ` James Cloos
2010-02-21 2:12 ` James Cloos
2010-02-19 21:22 ` Mike Fedyk
2010-02-19 21:44 ` James Cloos
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=201002150012.25572.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=cloos@jhcloos.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--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).