[lkml]   [2002]   [Oct]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC][PATCH] linux-2.5.34_vsyscall_A0
    One reason gettimeofday ends up being important is that several
    databases call it a lot. They use it to build up a transaction id. Under
    big transaction loads, even the fast linux syscall path ends up being a
    bottleneck. Also, on NUMA machines the data used for time of day (xtime)
    ends up being a significant portion of the cache traffic.

    It would be great to rework the whole TSC time of day stuff to work with
    per cpu data and allow unsychronized TSC's like NUMA. The problem is
    that for fast user level access, there would need to be some way to find
    out the current CPU and avoid preemption/migration for a short period.
    It seems like the LDT stuff for per-thread data could provide the
    current cpu (and maybe current pid) somehow. And it would be possible
    to avoid preemption while in a vsyscall text page, some other Unix
    variants do this to implement portions of the thread library in kernel
    provided user text pages.

    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 13:30    [W:0.875 / U:108.516 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site