Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750987AbVLPATk (ORCPT ); Thu, 15 Dec 2005 19:19:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751102AbVLPATk (ORCPT ); Thu, 15 Dec 2005 19:19:40 -0500 Received: from mx2.suse.de ([195.135.220.15]:11232 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S1750987AbVLPATk (ORCPT ); Thu, 15 Dec 2005 19:19:40 -0500 Date: Fri, 16 Dec 2005 01:19:34 +0100 From: Andi Kleen To: Ravikiran G Thirumalai Cc: Andi Kleen , linux-kernel@vger.kernel.org, discuss@x86-64.org, Andrew Morton , dada1@cosmobay.com, "Shai Fultheim (Shai@scalex86.org)" Subject: Re: [discuss] [patch 3/3] x86_64: Node local pda take 2 -- node local pda allocation Message-ID: <20051216001934.GN23384@wotan.suse.de> References: <20051215023345.GB3787@localhost.localdomain> <20051215023748.GD3787@localhost.localdomain> <20051215094232.GX23384@wotan.suse.de> <20051215184704.GA3882@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051215184704.GA3882@localhost.localdomain> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 640 Lines: 17 > So are you suggesting I use alloc_bootmem_node and allocate PDA for > NR_CPUS? Continue to allocate the boot PDA of the BP statically - this should be ok because BP should be always on node 0 (or if you're paranoid about it you could also reallocate, but it's probably not needed) And for the APs you allocate the PDA in smpboot.c before actually sending the startup IPI to the AP. -Andi - 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/