[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0000013a932d456c-8f0cbbce-e3f7-4f2a-b051-7b093a8cfc7e-000000@email.amazonses.com>
Date: Wed, 24 Oct 2012 14:29:09 +0000
From: Christoph Lameter <cl@...ux.com>
To: andi@...stfloor.org
cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Joonsoo Kim <js1304@...il.com>,
David Rientjes <rientjes@...gle.com>,
Pekka Enberg <penberg@...nel.org>,
Glauber Costa <glommer@...allels.com>
Subject: Re: [PATCH v2 1/2] kmem_cache: include allocators code directly into
slab_common
On Wed, 24 Oct 2012, Glauber Costa wrote:
> Because of that, we either have to move all the entry points to the
> mm/slab.h and rely heavily on the pre-processor, or include all .c files
> in here.
Hmm... That is a bit of a radical solution. The global optimizations now
possible with the new gcc compiler include the ability to fold functions
across different linkable objects. Andi, is that usable for kernel builds?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists