Subject: Re: [uClinux-dev] Kernel 2.6 size increase - get_current()?
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: David McCullough <davidm@snapgear.com>
Cc: Bernardo Innocenti <bernie@develer.com>,
       Christoph Hellwig <hch@infradead.org>,
       "David S. Miller" <davem@redhat.com>, uclinux-dev@uclinux.org,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Greg Ungerer <gerg@snapgear.com>
In-Reply-To: <20030724120441.GC16168@beast>
References: <200307232046.46990.bernie@develer.com>
	 <200307240035.38502.bernie@develer.com>
	 <1058999786.6890.21.camel@dhcp22.swansea.linux.org.uk>
	 <200307240100.00632.bernie@develer.com> <20030724050655.GA11947@beast>
	 <1059046125.7993.11.camel@dhcp22.swansea.linux.org.uk>
	 <20030724120441.GC16168@beast>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: 
Message-Id: <1059058118.7998.15.camel@dhcp22.swansea.linux.org.uk>
Mime-Version: 1.0
Date: 24 Jul 2003 15:48:39 +0100
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 722
Lines: 17

On Iau, 2003-07-24 at 13:04, David McCullough wrote:
> So should the trend be away from inlining,  especially larger functions ?
> 
> I know on m68k some of the really simple inlines are actually smaller as
> an inline than as a function call.  But they have to be very simple,  or
> only used once.

Cool. As to trends well there are two conflicting ones - less inlines but
also more code because of adding fast paths to cut conditions down on normal
sequences of execution.


-
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/