All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Alex Nixon (Intern)" <Alex.Nixon@eu.citrix.com>
Cc: 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 08:45:23 -0700	[thread overview]
Message-ID: <487F6913.2000602@goop.org> (raw)
In-Reply-To: <0E902970173AF84089673FA54B7FE78A32906B@lonpexch01.citrite.net>

Alex Nixon (Intern) wrote:
> Yeah I've checked - the number of context switches seems to be around
> 60k regardless of whether CONFIG_PARAVIRT is switched on, and regardless
> of whether it's running in domu or native (-j4 on dual core)
>   

OK, just to be sure we're talking about the same thing, is kernbench 
displaying the context switch *rate*, or the total number of context 
switches during the build?

Peter is looking at vmstat, which is showing cs/sec.

    J

  parent reply	other threads:[~2008-07-17 15:45 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 [this message]
2008-07-17 16:04         ` Alex Nixon (Intern)
2008-07-17 16:11           ` Jeremy Fitzhardinge
2008-07-17 21:43             ` Andi Kleen
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=487F6913.2000602@goop.org \
    --to=jeremy@goop.org \
    --cc=Alex.Nixon@eu.citrix.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --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.