linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Andy Whitcroft <apw@canonical.com>
Cc: dhowells@redhat.com, tytso@mit.edu,
	Dave Airlie <airlied@gmail.com>, Dave Airlie <airlied@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Why is kslowd accumulating so much CPU time?
Date: Tue, 15 Jun 2010 19:07:48 +0100	[thread overview]
Message-ID: <18402.1276625268@redhat.com> (raw)
In-Reply-To: <AANLkTikxOwYQYSzNjEqRduTQvoUandnAsZzm5Auzgnaz@mail.gmail.com>

Andy Whitcroft <apw@canonical.com> wrote:

> I am seeing crunchy cursor behavior on boot on Ubuntu Lucid user space
> with the 2.6.35-rc3 kernel as well.  It pretty much always does that
> on boot, and often later as well.  Right now I have four of these
> chaps each consuming 9% of a CPU.  Though they definatly come and go.
> Very odd:
> 
>   938 root      15  -5     0    0    0 S    9  0.0   1:00.90 kslowd001
>  1048 root      15  -5     0    0    0 S    9  0.0   1:01.12 kslowd002
>   937 root      15  -5     0    0    0 S    8  0.0   1:00.92 kslowd000
>  1544 root      15  -5     0    0    0 D    8  0.0   1:00.55 kslowd003

Can you see what they're doing?

	watch -n0 cat /sys/kernel/debug/slow_work/runqueue

David

  parent reply	other threads:[~2010-06-15 18:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 18:36 Why is kslowd accumulating so much CPU time? Theodore Ts'o
2010-06-09 18:56 ` David Howells
2010-06-09 19:00 ` David Howells
2010-06-13  8:23 ` Dave Airlie
2010-06-13 19:49   ` tytso
2010-06-13 20:00     ` Dave Airlie
2010-06-14 18:42       ` Nick Bowler
2010-06-14 21:46         ` tytso
2010-06-15 17:25           ` Andy Whitcroft
2010-06-15 18:07           ` David Howells [this message]
2010-06-16 11:37             ` Andy Whitcroft
2010-06-16 13:33               ` Andy Whitcroft
2010-06-16 14:36               ` Nick Bowler
2010-06-16 14:55                 ` Andy Whitcroft
2010-06-17 13:25                   ` Nick Bowler

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=18402.1276625268@redhat.com \
    --to=dhowells@redhat.com \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=apw@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).