From: "Ray Lee" <ray-lk@madrabbit.org>
To: bdupree@techfinesse.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dynticks Causing High Context Switch Rate in ksoftirqd
Date: Thu, 29 Nov 2007 07:40:49 -0800 [thread overview]
Message-ID: <2c0942db0711290740y7c730fb3te629454462df3efe@mail.gmail.com> (raw)
In-Reply-To: <46738.67.173.156.207.1196304247.squirrel@www.techfinesse.net>
On Nov 28, 2007 6:44 PM, <bdupree@techfinesse.com> wrote:
> I built the same dynticks-enabled 2.6.23.9 kernel on a nearly identical
> system with minor changes to reflect the slightly different hardware.
> These two systems have identical MSI E7210 MasterX FA6R motherboards (same
> model and revision.) The differences are as follows:
>
> behemoth (using Slackware 10.2)
> -----------------------------------------------------------------
> dual 2.4 GHz Xeons 400 MHz FSB
> LSI 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI
> Newer SATA/PATA Intel PIIX drivers
>
> titan (using Slackware 11.0)
> -----------------------------------------------------------------
> dual 2.0 GHz Xeons 533 MHz FSB
> Creative Labs SB Audigy LS (using ALSA driver)
> Older IDE PATA Intel PIIX drivers
>
> The result is that "behemoth" continues to exhibit 155,000 context
> switches per second at idle while "titan" shows about 25 - 30 context
> switches per second. Note that motherboard BIOS'es are at the same
> revision and configured identically.
>
> I guess (ugh) it's time for me to pull the MPT-Fusion U320 HBA and the
> SATA disks out of "behemoth" and configure it with old style IDE drives to
> be as close as possible to "titan." Then I can add parts back and see when
> the problem occurs.
Well, the first thing that seems obvious is that you're using
different version of userspace, and the newer userspace is on the
system that behaves better.
The second thing that pops to mind: are you doing all these
measurements booted into single user mode (init=/bin/bash or
somesuch)? If not, then I don't think we can pin this on the hardware
quite yet.
next prev parent reply other threads:[~2007-11-29 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 2:44 Dynticks Causing High Context Switch Rate in ksoftirqd bdupree
2007-11-29 15:40 ` Ray Lee [this message]
[not found] ` <17931.144.160.98.31.1196356276.squirrel@www.techfinesse.net>
2007-11-29 17:38 ` Ray Lee
[not found] <fa.c70Wy8WHP3DOaDydQ2D94+Xxx/8@ifi.uio.no>
2007-11-27 4:36 ` 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
-- 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=2c0942db0711290740y7c730fb3te629454462df3efe@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--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