From: Andi Kleen <ak@suse.de>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [patch] i386: use C code for current_thread_info()
Date: 12 Jun 2006 10:10:09 +0200 [thread overview]
Message-ID: <p73slmasske.fsf@verdi.suse.de> (raw)
In-Reply-To: <200606112144.26705.s0348365@sms.ed.ac.uk>
Alistair John Strachan <s0348365@sms.ed.ac.uk> writes:
> On Sunday 11 June 2006 20:42, Jan Engelhardt wrote:
> > >Using C code for current_thread_info() lets the compiler optimize it.
> > >With gcc 4.0.2, kernel is smaller:
> > >
> > > text data bss dec hex filename
> > > 3645212 555556 312024 4512792 44dc18 2.6.17-rc6-nb-post/vmlinux
> > > 3647276 555556 312024 4514856 44e428 2.6.17-rc6-nb/vmlinux
> > > -------
> > > -2064
> >
> > If possible, can you or someone post the results for x86_64?
>
> Patch is for i386, x86_64's current_thread_info() is already C.
Actually read_pda() is inline assembly. But so far gcc/binutils don't support
%gs references in the way the kernel needs it directly, so it has
to stay this way.
-Andi
next prev parent reply other threads:[~2006-06-12 8:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 19:07 [patch] i386: use C code for current_thread_info() Chuck Ebbert
2006-06-11 19:33 ` Linus Torvalds
2006-06-11 19:42 ` Jan Engelhardt
2006-06-11 20:33 ` Jan Engelhardt
2006-06-11 20:44 ` Alistair John Strachan
2006-06-12 8:10 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-11 20:43 Chuck Ebbert
2006-06-11 21:05 ` Emmanuel Fleury
2006-06-12 17:14 Chuck Ebbert
2006-06-12 17:55 ` Adrian Bunk
2006-06-12 18:48 ` Andreas Mohr
2006-06-13 1:50 Chuck Ebbert
2006-06-13 6:43 ` Andreas Mohr
2006-06-13 9:27 ` Avi Kivity
2006-06-13 5:26 Albert Cahalan
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=p73slmasske.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
--cc=torvalds@osdl.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.