All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: bdupree@techfinesse.com, linux-kernel@vger.kernel.org
Subject: Re: Dynticks Causing High Context Switch Rate in ksoftirqd
Date: Tue, 27 Nov 2007 21:28:05 -0800	[thread overview]
Message-ID: <20071127212805.31f0de96.akpm@linux-foundation.org> (raw)
In-Reply-To: <474B9EC1.5020304@shaw.ca>

On Mon, 26 Nov 2007 22:36:17 -0600 Robert Hancock <hancockr@shaw.ca> wrote:

> bdupree@techfinesse.com wrote:
> > Question: Why is ksoftirqd eating about 5 to 10 percent of my CPU on an idle
> > system? The problem occurs if I config the kernel with tickless
> > support (i.e. CONFIG_TICK_ONESHOT=y).  (Thanks to "oprofile" for putting me
> > onto this.)
> > 
> > I have noted this same problem on kernel versions: 2.6.23.1, 2.6.23.8 and
> > 2.6.23.9
> > 
> > **************************************************************************
> > *** Output from "vmstat -n 1 10" -- Note very high context switch rate ***
> > *** This is on a idle machine!                                         ***
> > **************************************************************************
> > 
> > procs -----------memory---------- ---swap-- -----io---- --system--
> > ----cpu----
> >  r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy
> > id wa
> >  0  0      0 1925556   4768 116104    0    0   124     2    6  7538  1  2
> > 96  1
> >  0  0      0 1925556   4768 116104    0    0     0     0    2 147329  0  1
> > 99  0
> 
> What did oprofile show? It should be able to narrow down what 
> function(s) are responsible for the CPU usage..

Sigh.  I just asked a similar thing.   Let's look at the mail headers:



Message-ID: <41877.67.173.156.207.1196130992.squirrel@www.techfinesse.net>
...
From: bdupree@techfinesse.com


From: Robert Hancock <hancockr@shaw.ca>
...
In-reply-to: <fa.c70Wy8WHP3DOaDydQ2D94+Xxx/8@ifi.uio.no>


Please fix your email client so as to not break threading?

  parent reply	other threads:[~2007-11-28  5:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.c70Wy8WHP3DOaDydQ2D94+Xxx/8@ifi.uio.no>
2007-11-27  4:36 ` Dynticks Causing High Context Switch Rate in ksoftirqd Robert Hancock
2007-11-27  5:38   ` Arjan van de Ven
     [not found]   ` <1887.192.128.167.68.1196188273.squirrel@www.techfinesse.net>
2007-11-28  0:18     ` Robert Hancock
2007-11-28  5:28   ` Andrew Morton [this message]
2007-11-29  2:44 bdupree
2007-11-29 15:40 ` Ray Lee
     [not found]   ` <17931.144.160.98.31.1196356276.squirrel@www.techfinesse.net>
2007-11-29 17:38     ` Ray Lee
  -- strict thread matches above, loose matches on Subject: below --
2007-11-27  2:36 bdupree
2007-11-28  5:22 ` Andrew Morton
2007-11-28 11:20   ` Ingo Molnar

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=20071127212805.31f0de96.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bdupree@techfinesse.com \
    --cc=hancockr@shaw.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.