From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: hjl@lucon.org, arjan@redhat.com, torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] save 4 bytes in "thread_struct" by changing fs/gs to "unsigned short"
Date: Sun, 5 Jun 2005 15:51:51 -0300 [thread overview]
Message-ID: <20050605185151.GA19232@logos.cnet> (raw)
Hi HJLu, Linus, Arjan,
Now that all users of fs and gs fields of "thread_struct" have been switched
to use "mov" instead of "movl" (newer binutils requirement), why not save
4 bytes switching those fields to 16-bit data types.
No big deal, but as we say around here, "grain by grain the chicken gets fat".
--- a/include/asm-i386/processor.h.orig 2005-06-05 20:11:00.000000000 -0300
+++ b/include/asm-i386/processor.h 2005-06-05 20:11:44.000000000 -0300
@@ -439,8 +439,8 @@ struct thread_struct {
unsigned long sysenter_cs;
unsigned long eip;
unsigned long esp;
- unsigned long fs;
- unsigned long gs;
+ unsigned short fs;
+ unsigned short gs;
/* Hardware debugging registers */
unsigned long debugreg[8]; /* %%db0-7 debug registers */
/* fault info */
reply other threads:[~2005-06-06 0:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050605185151.GA19232@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=arjan@redhat.com \
--cc=hjl@lucon.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox