linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Mike Galbraith <efault@gmx.de>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
	RT <linux-rt-users@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch] clockevents: Reinstate the per cpu tick skew
Date: Wed, 28 Dec 2011 17:57:24 +0100	[thread overview]
Message-ID: <1325091444.2651.1.camel@laptop> (raw)
In-Reply-To: <1325084349.16165.22.camel@marge.simson.net>

On Wed, 2011-12-28 at 15:59 +0100, Mike Galbraith wrote:
> 
> > (and are you using a system where tsc/lapic can be used, or are you
> > using one of those boatanchors that need hpet?)
> 
> Box is an HP DL980, 64 x X7560. 

That smells like NHM-EX, aka boatanchor.


  reply	other threads:[~2011-12-28 16:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-24  9:06 3.0.14-rt31 + 64 cores = very bad jitter == highly synchronized tick? Mike Galbraith
2011-12-25  7:31 ` Mike Galbraith
2011-12-26  8:04   ` Mike Galbraith
2011-12-27  6:40 ` Mike Galbraith
2011-12-27  9:20   ` [patch] clockevents: Reinstate the per cpu tick skew Mike Galbraith
2011-12-28  5:17     ` Mike Galbraith
2011-12-28  8:22       ` Mike Galbraith
2011-12-28  9:59         ` Mike Galbraith
2011-12-28 13:35       ` Arjan van de Ven
2011-12-28 14:59         ` Mike Galbraith
2011-12-28 16:57           ` Peter Zijlstra [this message]
2011-12-28 17:28             ` Mike Galbraith
2011-12-29  7:22         ` Mike Galbraith
2011-12-28 13:32     ` Arjan van de Ven
2011-12-28 15:10       ` Mike Galbraith
2012-01-03  6:20         ` Mike Galbraith
2012-04-23  6:13           ` irq latency regression post af5ab277 - was " Mike Galbraith

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=1325091444.2651.1.camel@laptop \
    --to=a.p.zijlstra@chello.nl \
    --cc=arjan@linux.intel.com \
    --cc=efault@gmx.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).