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>] [day] [month] [year] [list]

Message-ID: <2c0942db0711290938q7be4268fg8b1249b24804482f@mail.gmail.com>
Date:	Thu, 29 Nov 2007 09:38:37 -0800
From:	"Ray Lee" <ray-lk@...rabbit.org>
To:	bdupree@...hfinesse.com,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: Dynticks Causing High Context Switch Rate in ksoftirqd

On Nov 29, 2007 9:11 AM,  <bdupree@...hfinesse.com> wrote:
>
> These are good points. However, on the Slack 10.2 box I repeated these
> measurements with all userspace code quiesced. No daemons running except
> for those that are kernel threads. Secondly, I do run dynticks kernels on
> other Slackware 10.2 boxen without these issues. The hardware may not be
> identical, e.g. Xeons with Intel E7501 chipsets or Opterons with AMD 8131
> chipsets, but I don't see any of this weirdness. Maybe I'll fire up Slack
> 10.2 on spare partition on the other (almost) identical machine and see if
> it exhibits this problem.

Any way you can narrow down the problem space will help, as there are
a lot of variables right now.

Also, please keep the kernel list CC:d so others who are lurking can
see what's going on, and not ask for duplicate data.
-
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/