public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Milton Miller <miltonm@bga.com>
Cc: Yong Zhang <yong.zhang0@gmail.com>,
	Borislav Petkov <bp@amd64.org>, Borislav Petkov <bp@alien8.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"markus@trippelsdorf.de" <markus@trippelsdorf.de>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"linux-tip-commits@vger.kernel.org" 
	<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:sched/urgent] sched: Fix cross-cpu clock sync on remote wakeups
Date: Fri, 03 Jun 2011 12:58:33 +0200	[thread overview]
Message-ID: <1307098713.2353.3099.camel@twins> (raw)
In-Reply-To: <1307098506.2353.3094.camel@twins>

On Fri, 2011-06-03 at 12:55 +0200, Peter Zijlstra wrote:
> On Fri, 2011-06-03 at 12:36 +0200, Peter Zijlstra wrote:
> > > Can we get some numbers for how often the two cases occur on some
> > > various workloads?
> > 
> > Sure, let me stick some counters in. 
> 
> Of 128765 IPIs, 17483 were with an empty list (boot + make -j64).
> 
> I didn't yet look at where those empty ones originated from.

After two more make clean; make -j64 cycles thats:

 250082:24793

So on this load its 10+:1.

  reply	other threads:[~2011-06-03 10:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30 17:39 Very high CPU values in top on idle system (3.0-rc1) Markus Trippelsdorf
2011-05-30 18:05 ` Peter Zijlstra
2011-05-30 18:23   ` Markus Trippelsdorf
2011-05-30 20:45     ` Markus Trippelsdorf
2011-05-30 22:12       ` Peter Zijlstra
2011-05-31  9:55         ` Peter Zijlstra
2011-05-31 10:04           ` Markus Trippelsdorf
2011-05-31 12:31           ` [tip:sched/urgent] sched: Fix cross-cpu clock sync on remote wakeups tip-bot for Peter Zijlstra
2011-05-31 12:56             ` Borislav Petkov
2011-05-31 13:11               ` Peter Zijlstra
2011-06-01  7:05                 ` Borislav Petkov
2011-06-01 10:36                   ` Peter Zijlstra
2011-06-01 15:50                     ` Borislav Petkov
2011-06-02  7:52                       ` Yong Zhang
2011-06-02 13:04                         ` Peter Zijlstra
2011-06-02 14:23                           ` Yong Zhang
2011-06-02 15:48                             ` Peter Zijlstra
2011-06-03  6:49                               ` Yong Zhang
2011-06-03  9:57                               ` Milton Miller
2011-06-03 10:36                                 ` Peter Zijlstra
2011-06-03 10:55                                   ` Peter Zijlstra
2011-06-03 10:58                                     ` Peter Zijlstra [this message]
2011-06-07 13:12                               ` Borislav Petkov
2011-06-07 13:16                                 ` Peter Zijlstra

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=1307098713.2353.3099.camel@twins \
    --to=peterz@infradead.org \
    --cc=bp@alien8.de \
    --cc=bp@amd64.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=miltonm@bga.com \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=yong.zhang0@gmail.com \
    /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