From: Pavel Machek <pavel@suse.cz>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: rfc/rft: use r10 as current on x86-64
Date: Wed, 23 Nov 2005 23:48:03 +0100 [thread overview]
Message-ID: <20051123224803.GE24220@elf.ucw.cz> (raw)
In-Reply-To: <20051122165204.GG1127@kvack.org>
Hi!
> The patch below converts x86-64 to use r10 as the current pointer instead
> of gs:pcurrent. This results in a ~34KB savings in the code segment of
> the kernel. I've tested this with running a few regular applications,
> plus a few 32 bit binaries. If this patch is interesting, it probably
> makes sense to merge the thread info structure into the task_struct so
> that the assembly bits for syscall entry can be cleaned up. Comments?
34KB smaller is nice, but is not it also 30% slower? Plus some inline
assembly *will* have %r10 hardcoded, no? I'd be afraid around crypto
code, for example.
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2005-11-23 22:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 16:52 Benjamin LaHaise
2005-11-22 17:10 ` Andi Kleen
2005-11-22 17:26 ` Benjamin LaHaise
2005-11-22 17:46 ` Brian Gerst
2005-11-22 17:55 ` Andreas Steinmetz
2005-11-23 22:48 ` Pavel Machek [this message]
2005-11-23 22:54 ` Benjamin LaHaise
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=20051123224803.GE24220@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=bcrl@kvack.org \
--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
all inboxes | Powered by JetHome®