[lkml]   [2004]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: 2.4.23aa2 (bugfixes and important VM improvements for the high end)
    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.

    Also, if there's paging the variable may be out of date by quite a
    long time, so mlock() should be used to remove that aspect of the delay.

    I don't know if such delays a problem for MySQL.

    -- Jamie
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:01    [W:0.019 / U:67.708 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site