[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200702130928.05838.andi@firstfloor.org>
Date: Tue, 13 Feb 2007 09:28:05 +0100
From: Andi Kleen <andi@...stfloor.org>
To: Arjan van de Ven <arjan@...radead.org>
Cc: Christoph Lameter <clameter@....com>,
Vojtech Pavlik <vojtech@...e.cz>, Jiri Bohac <jbohac@...e.cz>,
linux-kernel@...r.kernel.org, ssouhlal@...ebsd.org,
tglx@...utronix.de, johnstul@...ibm.com, zippel@...ux-m68k.org,
andrea@...e.de
Subject: Re: [patch 4/9] Remove the TSC synchronization on SMP machines
On Tuesday 13 February 2007 07:40, Arjan van de Ven wrote:
> On Mon, 2007-02-12 at 16:34 -0800, Christoph Lameter wrote:
> > On Fri, 2 Feb 2007, Andi Kleen wrote:
> >
> > > I've threatened to just disable RDTSC for ring 3 before, but it'll likely
> > > never happen because too many programs use it.
> >
> > Those programs are aware that they are fiddling around with low level
> > material but with this patchset we are going to have a non
> > monotonic time subsystem?
>
> no quite the opposite. gettimeofday() currently is NOT monotonic
> unfortunately.
Anytime it is non monotonic that's a bug. We've had bugs
like this before, but recently we're doing reasonably well. Of course
there can be always improvements, but in general I don't agree
with your statement, sorry. You can usually rely on it being monotonic,
short of the known limitations (e.g. don't run ntpd)
Usually it weren't really classical bugs, but more "hardware does
unexpected things under us". x86 hardware is a moving target unfortunately.
> With this patchseries it actually has a better chance of
> becoming that...
ntpd problem is fundamental, nothing will change that. However
it doesn't seem to be a big one in practice.
-Andi
-
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