linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
	linux-arch@vger.kernel.org
Subject: Re: [patch] Remove the per cpu tick skew
Date: Wed, 28 Jul 2010 16:50:40 -0700	[thread overview]
Message-ID: <AANLkTim3h4VNqF97d++k4_4g-4hnw57YXJSQgSEP4S7m@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikZ_RHHv9cudUh8pp9H8MtKO8Rsr+eboupv49xD@mail.gmail.com>

On Wed, Jul 28, 2010 at 1:26 PM, john stultz <johnstul@us.ibm.com> wrote:
> On Tue, Jul 27, 2010 at 9:02 PM, Arjan van de Ven <arjan@infradead.org> wrote:
>> Historically, Linux has tried to make the regular timer tick on the various
>> CPUs not happen at the same time, to avoid contention on xtime_lock.
>>
>> Nowadays, with the tickless kernel, this contention no longer happens
>> since time keeping and updating are done differently. In addition,
>> this skew is actually hurting power consumption in a measurable
>> way on many-core systems.
>>
>
> I'll give it a spin against -rt and see if we show any latency jumps.

In my testing on a 8way box, I didn't see any concerning latencies
with this patch running cyclictest or a FIFO99 gtod loop.

thanks
-john

  reply	other threads:[~2010-07-28 23:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28  4:02 [patch] Remove the per cpu tick skew Arjan van de Ven
2010-07-28 20:26 ` john stultz
2010-07-28 23:50   ` john stultz [this message]
2010-07-30  7:27 ` Nick Piggin
2010-07-30  7:27   ` Nick Piggin
2010-07-30 13:57   ` Arjan van de Ven
2010-07-30 13:57     ` Arjan van de Ven

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=AANLkTim3h4VNqF97d++k4_4g-4hnw57YXJSQgSEP4S7m@mail.gmail.com \
    --to=johnstul@us.ibm.com \
    --cc=arjan@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).