From: Benjamin LaHaise <bcrl@redhat.com>
To: Ulrich Drepper <drepper@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, 5 Mar 2003 21:08:56 -0500 [thread overview]
Message-ID: <20030305210856.B16093@redhat.com> (raw)
In-Reply-To: <3E668267.5040203@redhat.com>; from drepper@redhat.com on Wed, Mar 05, 2003 at 03:04:07PM -0800
On Wed, Mar 05, 2003 at 03:04:07PM -0800, Ulrich Drepper wrote:
> I wouldn't want to either in your position. You caused this whole mess
> and now you're not willing to fix it.
I disagree. We don't need to use a segment register to get the thread
library equivalent of "current". Changing the segment registers on a
per process basis is a waste of time in the context switch. 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. Make the users of threads suffer, not
every single application and syscall in the system.
-ben
--
Junk email? <a href="mailto:aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-03-06 1:58 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 [this message]
2003-03-06 3:52 ` Ulrich Drepper
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=20030305210856.B16093@redhat.com \
--to=bcrl@redhat.com \
--cc=ak@suse.de \
--cc=drepper@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.