Messages in this thread | | | Date | Sun, 7 Mar 2004 12:55:10 +0100 | From | Ingo Molnar <> | Subject | Re: 2.4.23aa2 (bugfixes and important VM improvements for the high end) |
| |
* Jamie Lokier <jamie@shareable.org> wrote:
> Ingo Molnar wrote: > > if mysql in fact calls time() frequently, then it should rather start a > > worker thread that updates a global time variable every second. > > That has the same problem as discussed later in this thread with > vsyscall-time: the worker thread may not run immediately it is woken, > and also setitimer() and select() round up the delay a little more > then expected, so sometimes the global time variable will be out of > date and misordered w.r.t. gettimeofday() and stat() results of > recently modified files.
we dont have any guarantees wrt. the synchronization of the time() and the gettimeofday() clocks - irrespective of vsyscalls, do we?
Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |