From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932625AbXKOStw (ORCPT ); Thu, 15 Nov 2007 13:49:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1764788AbXKOStk (ORCPT ); Thu, 15 Nov 2007 13:49:40 -0500 Received: from relay1.sgi.com ([192.48.171.29]:37948 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1759533AbXKOStj (ORCPT ); Thu, 15 Nov 2007 13:49:39 -0500 Date: Thu, 15 Nov 2007 10:49:37 -0800 (PST) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Jonathan Corbet cc: andi@firstfloor.org, David Miller , akpm@linux-foundation.org, linux-kernel@vger.kernel.org, dada1@cosmosbay.com, schwidefsky@de.ibm.com Subject: Re: [patch 01/28] cpu alloc: The allocator In-Reply-To: <20071113.215306.78239549.davem@davemloft.net> Message-ID: References: <20071113.201853.40241484.davem@davemloft.net> <20071113.215306.78239549.davem@davemloft.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Well there is an LWN article now that also claims that the cpu_alloc patchset requires a large bss space. Sigh. See http://lwn.net/Articles/257828/ Not true! 44 bytes is reasonable. christoph@stapp:~/linux-2.6$ size mm/cpu_alloc.o text data bss dec hex filename 5625 36 44 5705 1649 mm/cpu_alloc.o Need to separate out the virtualization into a separate patch in V2 to make clear that it is there.