> > so it appears that this lowlevel x86 performance bug(?) is more than 11
> > years old! :-)
>
> Probably 386's were not optimized for %fs==%gs==0 case?
>
> BTW does it really make a difference for the CPU?
whether %fs/%gs is 0 or not? With the current 2.5.3-pre6 task switching
code there definitely is a performance difference, because we optimize the
'both values are 0' case. With the original TSS-based task switching
microcode i suspect it made a difference as well. (switching between two
different %fs/%gs values should be slower.)
Ingo
-
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/