mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ray Lee" <ray-lk@madrabbit.org>
To: bdupree@techfinesse.com,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Dynticks Causing High Context Switch Rate in ksoftirqd
Date: Thu, 29 Nov 2007 09:38:37 -0800	[thread overview]
Message-ID: <2c0942db0711290938q7be4268fg8b1249b24804482f@mail.gmail.com> (raw)
In-Reply-To: <17931.144.160.98.31.1196356276.squirrel@www.techfinesse.net>

On Nov 29, 2007 9:11 AM,  <bdupree@techfinesse.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.

  parent reply	other threads:[~2007-11-29 17:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
     [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=2c0942db0711290938q7be4268fg8b1249b24804482f@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
all inboxes | Powered by JetHome®