From: Andi Kleen <andi@firstfloor.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Alex Nixon (Intern)" <Alex.Nixon@eu.citrix.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ian Campbell <Ian.Campbell@eu.citrix.com>
Subject: Re: Large increase in context switch rate
Date: Thu, 17 Jul 2008 23:43:24 +0200 [thread overview]
Message-ID: <87mykgrxtv.fsf@basil.nowhere.org> (raw)
In-Reply-To: <487F6F1F.2030808@goop.org> (Jeremy Fitzhardinge's message of "Thu, 17 Jul 2008 09:11:11 -0700")
Jeremy Fitzhardinge <jeremy@goop.org> writes:
>
> OK, but that still doesn't account for the relatively large increase
> from 2.6.18 -> 2.6.26. You're using HZ=100 in both cases, I presume.
>
> The other variable is NOHZ and highres timers. You could try turning
> those off in 2.6.26. Also, CONFIG_PREEMPT could well make a
> difference. 2.6.18-xen doesn't support CONFIG_PREEMPT at all, but
> pvops(-xen) does.
If it's that easily reproducible you could just bisect it?
-Andi
next prev parent reply other threads:[~2008-07-17 21:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 18:54 Large increase in context switch rate Jeremy Fitzhardinge
2008-07-17 9:17 ` Peter Zijlstra
2008-07-17 15:02 ` Jeremy Fitzhardinge
2008-07-17 15:14 ` Alex Nixon (Intern)
2008-07-17 15:21 ` Peter Zijlstra
2008-07-17 15:45 ` Jeremy Fitzhardinge
2008-07-17 16:04 ` Alex Nixon (Intern)
2008-07-17 16:11 ` Jeremy Fitzhardinge
2008-07-17 21:43 ` Andi Kleen [this message]
2008-07-18 17:00 ` Alex Nixon (Intern)
2008-07-23 9:34 ` Alex Nixon (Intern)
2008-07-23 13:54 ` Andi Kleen
2008-07-24 1:26 ` Nick Piggin
2008-07-25 11:31 ` Alex Nixon
2008-07-25 11:39 ` Peter Zijlstra
2008-07-25 14:54 ` Jeremy Fitzhardinge
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=87mykgrxtv.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=Alex.Nixon@eu.citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.