From: Matt Mackall <mpm@selenic.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC][PATCH] Reduce number of pointer derefs in various files (kernel/exit.c used as example)
Date: Thu, 8 Dec 2005 17:46:59 -0800 [thread overview]
Message-ID: <20051209014658.GA11856@waste.org> (raw)
In-Reply-To: <20051206221528.GA12358@elte.hu>
On Tue, Dec 06, 2005 at 11:15:28PM +0100, Ingo Molnar wrote:
>
> * Jesper Juhl <jesper.juhl@gmail.com> wrote:
>
> > Ohh, and before I forget, besides the fact that this should speed
> > things up a little bit it also has the added benefit of reducing the
> > size of the generated code. The original kernel/exit.o file was 19604
> > bytes in size, the patched one is 19508 bytes in size.
>
> nice. Just to underline your point, on x86, with gcc 4.0.2, i'm getting
> this with your patch:
>
> text data bss dec hex filename
> 11077 0 0 11077 2b45 exit.o.orig
> 10997 0 0 10997 2af5 exit.o
>
> so 80 bytes shaved off. I think such patches also increase readability.
Readability improved: good.
37 lines of patch for 80-100 bytes saved: not so good.
So while this is a good style direction, I don't think it's worth the
churn. And unlike kzalloc and the like, this particular optimization
is perfectly doable by a compiler. So I'd rather wait for the compiler
to get smarter than change code for such modest improvements.
FYI, much other low-hanging size-reduction fruit remains in the
kernel. Lots of it in the form of duplicate code.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2005-12-09 1:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 22:02 [RFC][PATCH] Reduce number of pointer derefs in various files (kernel/exit.c used as example) Jesper Juhl
2005-12-06 22:15 ` Ingo Molnar
2005-12-09 1:46 ` Matt Mackall [this message]
2005-12-09 8:14 ` Oliver Neukum
2005-12-09 18:22 ` Matt Mackall
2005-12-09 10:29 ` Ingo Molnar
2005-12-09 18:34 ` Matt Mackall
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=20051209014658.GA11856@waste.org \
--to=mpm@selenic.com \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.