From: Ingo Molnar <mingo@elte.hu>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Oleg Verych <olecom@flower.upol.cz>
Subject: Re: [PATCH 1/2] Colored kernel output (run3)
Date: Sun, 7 Oct 2007 18:59:53 +0200 [thread overview]
Message-ID: <20071007165953.GB32139@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0710071849240.16301@fbirervta.pbzchgretzou.qr>
* Jan Engelhardt <jengelh@computergmbh.de> wrote:
> > vmlinux:
> > text data bss dec hex filename
> > 7732358 1157269 401408 9291035 8dc51b vmlinux.before
> > 7732374 1157269 401408 9291051 8dc52b vmlinux.after
> >
> >16 bytes, or 0.0002% of the total text size. So there's in essence no
> >text overhead to talk about. So the text overhead argument is a red
> >herring.
>
> 16 bytes, huh? Can't be. That would be like, perhaps 5, x86 instructions.
yes, it's that low, and it's with the feature disabled. (People who
enable a feature will of course see text size increase, but that's
beside the point.)
Ingo
next prev parent reply other threads:[~2007-10-07 17:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0710062147370.20637@fbirervta.pbzchgretzou.qr>
2007-10-06 20:09 ` [PATCH 1/2] Colored kernel output (run3) Jan Engelhardt
2007-10-06 22:52 ` Alan Cox
2007-10-07 16:38 ` Ingo Molnar
2007-10-07 16:44 ` Jan Engelhardt
2007-10-07 16:44 ` Ingo Molnar
2007-10-07 16:54 ` Jan Engelhardt
2007-10-07 16:59 ` Ingo Molnar [this message]
2007-10-07 17:03 ` Jan Engelhardt
2007-10-07 17:08 ` Ingo Molnar
2007-10-08 23:12 ` Antonino A. Daplas
2007-10-08 23:31 ` Jan Engelhardt
2007-10-08 23:53 ` Antonino A. Daplas
2007-10-09 21:36 ` Bill Davidsen
2007-10-06 20:10 ` [PATCH 2/2] " Jan Engelhardt
2007-10-06 21:25 ` Oleg Verych
2007-10-06 21:27 ` Jan Engelhardt
2007-10-06 22:28 ` On text size and run time if config is "n", " Oleg Verych
2007-10-06 22:20 ` Jan Engelhardt
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=20071007165953.GB32139@elte.hu \
--to=mingo@elte.hu \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
/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.