[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1248097754.15751.8867.camel@twins>
Date: Mon, 20 Jul 2009 15:49:14 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Arjan van de Ven <arjan@...radead.org>
Cc: john stultz <johnstul@...ibm.com>,
Thomas Gleixner <tglx@...utronix.de>,
lkml <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...x.de>, Ingo Molnar <mingo@...e.hu>,
Andi Kleen <ak@...e.de>, nikolag@...ibm.com,
Darren Hart <dvhltc@...ibm.com>
Subject: Re: [RFC][PATCH] Introduce CLOCK_REALTIME_COARSE
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 ;-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists