From: Peter Zijlstra <peterz@infradead.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: john stultz <johnstul@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@tglx.de>, Ingo Molnar <mingo@elte.hu>,
Andi Kleen <ak@suse.de>,
nikolag@ca.ibm.com, Darren Hart <dvhltc@us.ibm.com>
Subject: Re: [RFC][PATCH] Introduce CLOCK_REALTIME_COARSE
Date: Mon, 20 Jul 2009 15:49:14 +0200 [thread overview]
Message-ID: <1248097754.15751.8867.camel@twins> (raw)
In-Reply-To: <20090720063305.2ad49d40@infradead.org>
On Mon, 2009-07-20 at 06:33 -0700, Arjan van de Ven wrote:
> > Maybe power64, sparc64 and s390x qualify, but certainly nothing on x86
> > does.
>
> the x86 on my desk disagrees.
>From what I know even nehalem doesn't have fully synced tscs when your
machine is large enough, and the timers are still a tad expensive.
Maybe your desktop is next-gen? 't would be nice to finally have an x86
that has usable clock and timer hardware.
I'm sure tglx would be pleasantly surprised :-)
> > Furthermore, on the software side we'd need a few modifications, such
> > as doing lazy accounting for things like u/s-time which currently
> > rely on the tick and moving the load-balancing into a hrtimer.
>
> I thought the load balancer no longer runs as a timer.. but I could
> well be wrong.
It doesn't but it does need wakeup kicks, which are currently done from
the tick.
And I'm not at all disagreeing that we want the tick gone, I'm just
pointing out there's some challenges ahead still ;-)
next prev parent reply other threads:[~2009-07-20 13:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 23:39 [RFC][PATCH] Introduce CLOCK_REALTIME_COARSE john stultz
2009-07-18 8:30 ` Thomas Gleixner
2009-07-18 22:09 ` john stultz
2009-07-18 22:30 ` Arjan van de Ven
2009-07-20 11:17 ` Peter Zijlstra
2009-07-20 12:22 ` Paul E. McKenney
2009-07-20 13:33 ` Arjan van de Ven
2009-07-20 13:49 ` Peter Zijlstra [this message]
2009-07-22 21:39 ` Josh Triplett
2009-07-21 22:31 ` john stultz
2009-07-22 1:26 ` john stultz
2009-08-01 12:21 ` Andy Lutomirski
2009-07-18 12:09 ` Ingo Molnar
2009-07-18 22:20 ` john stultz
2009-07-19 3:00 ` Chris Snook
2009-07-19 6:14 ` Arjan van de Ven
2009-07-19 6:48 ` Nicholas Miell
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=1248097754.15751.8867.camel@twins \
--to=peterz@infradead.org \
--cc=ak@suse.de \
--cc=arjan@infradead.org \
--cc=dvhltc@us.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nikolag@ca.ibm.com \
--cc=tglx@linutronix.de \
--cc=tglx@tglx.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