>When you actually end up doing a context switch, the return predictor is
>hosed anyway - there's no way it can know what is going on, as the stack
I guess that also when we return in user mode (return_all) we lose the
return predictor...
>entry for the return path, which is good. The point being that it is not
>at all obvious which code is actually the faster one.
Thanks.
Andrea Arcangeli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/