[lkml]   [2003]   [Mar]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Better CLONE_SETTLS support for Hammer
Hash: SHA1

Benjamin LaHaise wrote:
> using the TLS segment everywhere slows everything down
> a tiny bit. Don't do it for unthreaded programs.

You completely (still!) fail to understand the issue. How can I take
somebody who suggest using the stack as a pseudo thread register
serious? You don't see the impact of this so you don't recognize who
absolutely absurd this is.

Wrt inthreaded apps: either TLS is used everywhere or not at all.
Single threaded code uses library code which relies on TLS. And since
TLS is part of the ABI there is not question about the "not at all".
The remaining issue is how to do it with the least impact. For this
I've proposed a method which does this (according to Andi's
measurements) with the least impact.

And nobody forces you to use the standard runtime environment. Go on,
create your own. Then you won't have any penalties except one single
'if' in the context switching code which you hopefully can live with.
Mark it with unlikely() for all I care.

- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at `---------------------------
Version: GnuPG v1.2.1 (GNU/Linux)


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: 2005-03-22 13:33    [W:0.065 / U:12.292 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site