lkml.org 
[lkml]   [2006]   [Jun]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: [discuss] Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
    Date

    > Probably I have not explained it correctly:
    > - The "information page" (that includes the current CPU no.) is not a
    > per CPU page

    If it isn't then you can't figure out the current CPU/node for a thread.

    Anyways I think we're talking past each other. Your approach might
    even work on ia64 (at least if you're willing to add a lot of cost
    to the context switch). You presumably could implement vgetcpu()
    internally with an approach like this (although with IA64's fast
    EPC calls it seems a bit pointless)

    It just won't work on x86.

    -Andi
    -
    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/

    \
     
     \ /
      Last update: 2006-06-19 10:57    [W:0.019 / U:33.096 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site