linux-kernel - Re: Dynticks Causing High Context Switch Rate in ksoftirqd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2c0942db0711290740y7c730fb3te629454462df3efe@mail.gmail.com>
Date:	Thu, 29 Nov 2007 07:40:49 -0800
From:	"Ray Lee" <ray-lk@...rabbit.org>
To:	bdupree@...hfinesse.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Dynticks Causing High Context Switch Rate in ksoftirqd

On Nov 28, 2007 6:44 PM, <bdupree@...hfinesse.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/