mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Dave Airlie <airlied@redhat.com>, David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Why is kslowd accumulating so much CPU time?
Date: Wed, 09 Jun 2010 14:36:00 -0400	[thread overview]
Message-ID: <E1OMQ88-0002a1-Gb@closure.thunk.org> (raw)


My laptop is running 2.6.35-rc2 (plus a few patches) and after not quite
four hours of beeing booted (3:45 to be precise), top shows that kslowd
has accumulated as surprising amount of CPU time.  From top display:

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 6173 root      15  -5     0    0    0 S    6  0.0  10:42.91 kslowd001
 1219 root      15  -5     0    0    0 S    5  0.0  11:00.68 kslowd000
 1765 root      15  -5     0    0    0 S    5  0.0  10:59.20 kslowd002
 6784 root      15  -5     0    0    0 S    4  0.0  10:34.37 kslowd003
 4946 root      20   0  144m  34m  17m S    3  0.9   2:24.62 Xorg

This came up because I was trying to figure out why mouse response was
being so jerky.  There aren't that many users of slow-work, and given
that I'm not using cifs, fscache, gfs2, my suspicions are falling on
drivers/gpu/drm/drm_crtc_helper.c (Would this be something that would be
in use on a Lenovo T400 laptop?)

Is there any way to easily see what is scheduling themselves to use the
slow workqueue?

Thanks,

						- Ted

             reply	other threads:[~2010-06-09 18:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 18:36 Theodore Ts'o [this message]
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
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=E1OMQ88-0002a1-Gb@closure.thunk.org \
    --to=tytso@mit.edu \
    --cc=airlied@redhat.com \
    --cc=dhowells@redhat.com \
    --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

Powered by JetHome