Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754806AbZA1R6c (ORCPT ); Wed, 28 Jan 2009 12:58:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752370AbZA1R54 (ORCPT ); Wed, 28 Jan 2009 12:57:56 -0500 Received: from smtp3.ultrahosting.com ([74.213.175.254]:46640 "EHLO smtp.ultrahosting.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752335AbZA1R5w (ORCPT ); Wed, 28 Jan 2009 12:57:52 -0500 Date: Wed, 28 Jan 2009 11:48:27 -0500 (EST) From: Christoph Lameter X-X-Sender: cl@qirst.com To: "Luck, Tony" cc: Rick Jones , David Miller , "tj@kernel.org" , "rusty@rustcorp.com.au" , "mingo@elte.hu" , "herbert@gondor.apana.org.au" , "akpm@linux-foundation.org" , "hpa@zytor.com" , "brgerst@gmail.com" , "ebiederm@xmission.com" , "travis@sgi.com" , "linux-kernel@vger.kernel.org" , "steiner@sgi.com" , "hugh@veritas.com" , "netdev@vger.kernel.org" , "mathieu.desnoyers@polymtl.ca" , "linux-ia64@vger.kernel.org" Subject: RE: [PATCH] percpu: add optimized generic percpu accessors In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA35F317617@orsmsx505.amr.corp.intel.com> Message-ID: References: <200901271213.18605.rusty@rustcorp.com.au> <497E705B.5000302@kernel.org> <20090127.134747.153565246.davem@davemloft.net> <497F8F02.9000603@hp.com> <57C9024A16AD2D4C97DC78E552063EA35F317617@orsmsx505.amr.corp.intel.com> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1015 Lines: 29 On Tue, 27 Jan 2009, Luck, Tony wrote: > Managing a larger space could be done ... but at the expense of making > the Alt-DTLB miss handler do a memory lookup to find the physical address > of the per-cpu page needed (assuming that we allocate a bunch of random > physical pages for use as per-cpu space rather than a single contiguous > block of physical memory). We cannot resize the area by using a single larger TLB entry? > When do we know the total amount of per-cpu memory needed? > 1) CONFIG time? Would be easiest. > 2) Boot time? We could make the TLB entry size configurable with a kernel parameter > 3) Arbitrary run time? We could reserve a larger virtual space and switch TLB entries as needed? We would need do get larger order pages to do this. -- 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/