From: Ulrich Drepper <drepper@redhat.com>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: Andi Kleen <ak@suse.de>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Better CLONE_SETTLS support for Hammer
Date: Wed, 05 Mar 2003 19:52:20 -0800 [thread overview]
Message-ID: <3E66C5F4.5000106@redhat.com> (raw)
In-Reply-To: <20030305210856.B16093@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Benjamin LaHaise wrote:
> Instead,
> making x86-64 TLS support based off of the stack pointer, or even using
> a fixed per-cpu segment register such that gs:0 holds the pointer to the
> thread "current" would be better.
Gee, here is somebody who knows about thread APIs and ABIs. You're
really embarrassing yourself.
> Make the users of threads suffer, not
> every single application and syscall in the system.
Whether you like it or not, people are using threads. TLS requires a
thread register even in single-threaded applications. The mechanism I
proposed would use segments if <4GB addresses can be allocated,
otherwise fall back to prctl(ARCH_SET_FS). This is about as good as you
can get it.
Remove anything and hammer is the only architecture without good thread
support which undoubtedly makes you happy but almost nobody else.
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+ZsX02ijCOnn/RHQRAv87AJ4hHmL0N8ckGGsqROBk439jiUPAVgCgi/1K
NayzBhn7WQwjGATGaDzv0Pc=
=JXCv
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-03-06 3:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 18:55 Better CLONE_SETTLS support for Hammer Ulrich Drepper
2003-03-05 19:06 ` Andi Kleen
2003-03-05 19:25 ` Ulrich Drepper
2003-03-05 21:19 ` Andi Kleen
2003-03-05 19:32 ` Ulrich Drepper
2003-03-05 21:21 ` Andi Kleen
2003-03-05 23:04 ` Ulrich Drepper
2003-03-06 1:05 ` Andi Kleen
2003-03-06 3:53 ` Ulrich Drepper
2003-03-06 4:14 ` Ulrich Drepper
2003-03-06 10:27 ` Andi Kleen
2003-03-06 18:58 ` Ulrich Drepper
2003-03-06 19:09 ` Andi Kleen
2003-03-06 2:08 ` Benjamin LaHaise
2003-03-06 3:52 ` Ulrich Drepper [this message]
2003-03-06 5:29 ` Benjamin LaHaise
2003-03-06 5:47 ` Ulrich Drepper
2003-03-06 5:33 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E66C5F4.5000106@redhat.com \
--to=drepper@redhat.com \
--cc=ak@suse.de \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).