Message-Id: <200307250716.h6P7G8j05338@Port.imtp.ilyichevsk.odessa.ua>
Content-Type: text/plain; charset=US-ASCII
From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Reply-To: vda@port.imtp.ilyichevsk.odessa.ua
To: filia@softhome.net, linux-kernel@vger.kernel.org
Subject: Re: [uClinux-dev] Kernel 2.6 size increase - get_current()?
Date: Fri, 25 Jul 2003 10:25:31 +0300
References: <cwQJ.3BO.29@gated-at.bofh.it> <cArg.74D.11@gated-at.bofh.it> <3F1F9531.2050204@softhome.net>
In-Reply-To: <3F1F9531.2050204@softhome.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 994
Lines: 21

On 24 July 2003 11:13, Ihar \"Philips\" Filipau wrote:
>     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 
> 'better_inline'.
>     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...

Which inlines? Let the list know
--
vda
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/