Re: [RFC][PATCH] 2.6.0-test11 sched_clock() broken for "drifty ITC"

From: Ingo Molnar <>
Date: 2003-12-21 03:36:28
* Nick Piggin <> wrote:

> I'm just thinking that computers with unsynched clocks have less need
> for good interactivity, but thats probably too narrow and x86 a view
> anyway.

it's also a matter of predictable behavior. The scheduler should not
behave differently just because there's no synchronized clock. 
Behavioral forks like that tend to come back and cause trouble later.

To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to
More majordomo info at
Received on Sat Dec 20 11:37:28 2003

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:21 EST