From: email@example.com (bill davidsen)
Subject: Re: [uClinux-dev] Kernel 2.6 size increase - get_current()?
Date: 25 Jul 2003 18:36:08 GMT [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In article <3F1F9531.email@example.com>,
Ihar \"Philips\" Filipau <firstname.lastname@example.org> wrote:
| Just curious.
| Is there any way to guess inline from inline?
| I mean 'inline' which means 'this has to be inlined or it will
| break' and 'inline' which means 'inline this please - it adds only 10k
| of code bloat and improve performance in my suppa-puppa-bench by 0.000001%!'
| Strictly speaking - separate 'inline' to 'require_inline' and
| So people who really care about image size - can turn
| 'better_inline' into void, without harm to functionality.
| Actually I saw real performance improvements on my Pentium MMX 133
| (it has $i16k+$d16k of caches I beleive) when I was cutting some of
| inlines out. and I'm not talking about (cache poor) embedded systems...
Actually you have a very diferent CPU to memory bandwidth ratio than a
processor manufactured in this millenium. I use a system like that for
test, but please don't optimize for it!
Speculation of the day: I suspect that on some laptops which run
seriously slower when on battery, the CPU/memory speed changes enough
that you could see and measure better performance with a 'slow' and a
Speculation, since I'm sure the gain would be down in the noise, one of
those 'difference without a distinction' things.
bill davidsen <email@example.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2003-07-25 18:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cwQJ.3BO.firstname.lastname@example.org>
[not found] ` <cypH.5dM.email@example.com>
[not found] ` <cyza.5lN.firstname.lastname@example.org>
[not found] ` <cArg.74D.email@example.com>
2003-07-24 8:13 ` [uClinux-dev] Kernel 2.6 size increase - get_current()? Ihar "Philips" Filipau
2003-07-25 7:25 ` Denis Vlasenko
2003-07-25 18:36 ` bill davidsen [this message]
[not found] <d2nx.4QV.firstname.lastname@example.org>
[not found] ` <dbTZ.5Z5.email@example.com>
2003-07-25 15:37 ` Ihar "Philips" Filipau
2003-07-24 8:27 Ihar "Philips" Filipau
2003-07-24 11:50 ` David McCullough
-- strict thread matches above, loose matches on Subject: below --
2003-07-23 18:46 Kernel 2.6 size increase Bernardo Innocenti
2003-07-23 20:22 ` [uClinux-dev] " David S. Miller
2003-07-23 20:27 ` Christoph Hellwig
2003-07-23 22:35 ` [uClinux-dev] Kernel 2.6 size increase - get_current()? Bernardo Innocenti
2003-07-23 22:37 ` Alan Cox
2003-07-23 23:00 ` Bernardo Innocenti
2003-07-24 5:06 ` David McCullough
2003-07-24 11:28 ` Alan Cox
2003-07-24 12:04 ` David McCullough
2003-07-24 14:48 ` Alan Cox
2003-07-25 18:25 ` bill davidsen
2003-07-24 15:30 ` Hollis Blanchard
2003-07-24 19:37 ` Alan Cox
2003-07-24 19:51 ` Hollis Blanchard
2003-07-24 21:20 ` J.A. Magallon
2003-07-25 4:22 ` Otto Solares
2003-07-25 14:38 ` Hollis Blanchard
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).