[lkml]   [2006]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [discuss] Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
    On Friday 16 June 2006 23:19, Chase Venters wrote:
    > On Fri, 16 Jun 2006, Andi Kleen wrote:
    > >> To this last point, it might be more reasonable to map in a page that
    > >> contained a new structure with a stable ABI, which mirrored some of
    > >> the task_struct information, and likely other useful information as
    > >> needs are identified in the future. In any case, it would be hard
    > >> to beat a single memory read for performance.
    > >
    > > That would mean making the context switch and possibly other
    > > things slower.
    > Well, if every process had a page of its own, what would the context
    > switch overhead be?

    For process zero, for thread quite high on x86 because you
    would need per CPU page tables. Doing that would be extremly
    nasty because you would potentially need to allocate a new
    set of page tables every time the process is scheduled to a new
    CPU it hasn't run on before.

    If you limit it to a process then you can't get the current CPU
    from such a mapping because a process can run threaded on
    multiple CPUs.

    My reference was more to high suggestion of keeping a second version
    of task_struct for export. That would require changing everything
    in task struct that is changed on switch_to and should be exported
    in the other function too.

    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: 2006-06-17 08:58    [W:0.022 / U:2.732 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site