From: David Howells <dhowells@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: dhowells@redhat.com, Dave Airlie <airlied@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Why is kslowd accumulating so much CPU time?
Date: Wed, 09 Jun 2010 19:56:52 +0100 [thread overview]
Message-ID: <21934.1276109812@redhat.com> (raw)
In-Reply-To: <E1OMQ88-0002a1-Gb@closure.thunk.org>
Theodore Ts'o <tytso@mit.edu> wrote:
> Is there any way to easily see what is scheduling themselves to use the
> slow workqueue?
Slow work has debugging. Turn on:
CONFIG_SLOW_WORK_DEBUG=y
then do:
watch -n0 cat /sys/kernel/debug/slow_work/runqueue
David
next prev parent reply other threads:[~2010-06-09 18:56 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 [this message]
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
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=21934.1276109812@redhat.com \
--to=dhowells@redhat.com \
--cc=airlied@redhat.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).