It's not true at all that they use a "default" MMU-enabled TLS scheme
- you need arch-specific kernel support for a context switched memory
block whether it's with an MMU, or non-SMP without an MMU.
I did not look into any code for this. I was told that it should be easy
and not (largely) arch specific to do TLS if you have an MMU and thus I
_supposed_ that an MMU region would be used for TLS which is different
per thread while the other memory is not. This seems quite logical to
me: having the TLS for each thread at the same virtual address and do
the switching in the same way as the process memory is switched (thus
quite "out of the box" and not arch specific).
Maybe not slower, but larger, surely?
I suppose so, but nowadays, memory is not a real issue any more... :-) .
-Michael
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
