public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: Mike Fedyk <mfedyk@mikefedyk.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: Fri, 19 Feb 2010 16:44:08 -0500	[thread overview]
Message-ID: <m3r5ognbnj.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <93cdabd21002191322g7ea13d8bk52f1545df913f07@mail.gmail.com> (Mike Fedyk's message of "Fri, 19 Feb 2010 13:22:45 -0800")

>>>>> "Mike" == Mike Fedyk <mfedyk@mikefedyk.com> writes:

Mike> On Sat, Feb 13, 2010 at 7:11 PM, James Cloos <cloos@jhcloos.com> 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.
>> 

Mike> Are you sure you're not running with any of the debugging options
Mike> enabled?  I see the same, but I have debugging enabled (rawhide
Mike> kernel).

There are some:

CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CFG80211_DEBUGFS=y
CONFIG_MAC80211_DEBUGFS=y
CONFIG_PNP_DEBUG_MESSAGES=y
CONFIG_FIREWIRE_OHCI_DEBUG=y
CONFIG_USB_SERIAL_DEBUG=m
CONFIG_DEBUG_FS=y
CONFIG_DEBUG_KERNEL=y
CONFIG_SCHED_DEBUG=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_MEMORY_INIT=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y

I forgot about /proc/sched_debug, but am back at -rc6 right now; I'll
post an example of /proc/sched_debug output during the issue when I'm
next in rc8 or later.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6

      reply	other threads:[~2010-02-19 21:44 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
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 [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=m3r5ognbnj.fsf@lugabout.jhcloos.org \
    --to=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 \
    --cc=mfedyk@mikefedyk.com \
    /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