public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: bdupree@techfinesse.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Dynticks Causing High Context Switch Rate in ksoftirqd
Date: Tue, 27 Nov 2007 18:18:58 -0600	[thread overview]
Message-ID: <474CB3F2.9020901@shaw.ca> (raw)
In-Reply-To: <1887.192.128.167.68.1196188273.squirrel@www.techfinesse.net>

bdupree@techfinesse.com wrote:
> Hello Robert,
> 
> I've attached additional detail on the config of the misbehaving system
> including output from oprofile and PowerTop. PowerTop output leads me to
> believe that maybe this is an interaction between my bridged ethernet
> setup and dynticks? Hmmm...

Don't know about that, your top wakeups are from br_stp_enable_bridge, 
but that is only 26 a second - that doesn't explain a context switch 
rate of 150,000 a second..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


  parent reply	other threads:[~2007-11-28  0:19 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 [this message]
2007-11-28  5:28   ` Andrew Morton
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=474CB3F2.9020901@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=bdupree@techfinesse.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