From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759738AbXKNCEE (ORCPT ); Tue, 13 Nov 2007 21:04:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755298AbXKNCDx (ORCPT ); Tue, 13 Nov 2007 21:03:53 -0500 Received: from relay1.sgi.com ([192.48.171.29]:38100 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754534AbXKNCDw (ORCPT ); Tue, 13 Nov 2007 21:03:52 -0500 Date: Tue, 13 Nov 2007 18:03:51 -0800 (PST) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: David Miller cc: andi@firstfloor.org, akpm@linux-foundation.org, linux-mm@vger.kernel.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.180158.169883244.davem@davemloft.net> Message-ID: References: <20071113.175208.168903694.davem@davemloft.net> <20071113.180158.169883244.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 On Tue, 13 Nov 2007, David Miller wrote: > From: Christoph Lameter > Date: Tue, 13 Nov 2007 17:57:15 -0800 (PST) > > > Hmmmm. cpu_alloc really does not need zeroed data. Just an address > > fixed by the compiler where stuff can be put. Can the loader do that > > somehow? > > Yes, and I think IA64 uses such a scheme for it's 64KB fixed > per-cpu TLB mapping thing doesn't it? The per cpu TLB mapping is virtually mapped. The real memory allocation behind it occurs dynamically from bootmem.