From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756211AbZALTBn (ORCPT ); Mon, 12 Jan 2009 14:01:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752758AbZALTBf (ORCPT ); Mon, 12 Jan 2009 14:01:35 -0500 Received: from nlpi025.sbcis.sbc.com ([207.115.36.54]:49592 "EHLO nlpi025.prodigy.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751239AbZALTBe (ORCPT ); Mon, 12 Jan 2009 14:01:34 -0500 Date: Mon, 12 Jan 2009 13:00:46 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@quilx.com To: "Eric W. Biederman" cc: Rusty Russell , Tejun Heo , Ingo Molnar , travis@sgi.com, Linux Kernel Mailing List , "H. Peter Anvin" , Andrew Morton , steiner@sgi.com, Hugh Dickins Subject: Re: regarding the x86_64 zero-based percpu patches In-Reply-To: Message-ID: References: <49649814.4040005@kernel.org> <20090107120225.GA30651@elte.hu> <49649C65.6000706@kernel.org> <200901101716.04220.rusty@rustcorp.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: -2.6 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 12 Jan 2009, Eric W. Biederman wrote: > > There are 2M TLB entries on x86_64. If we really get into a high usage > > scenario then the 2M entry makes sense. Average server memory sizes likely > > already are way beyond 10G per box. The higher that goes the more > > reasonable the 2M TLB entry will be. > > 2M of per cpu data doesn't make sense, and likely indicates a design > flaw somewhere. It just doesn't make sense to have large amounts of > data allocated per cpu. Some data is not small. MIB data is allocated per cpu etc etc > What would be better is simply to: > - Require a lock to access another cpus per cpu data. > - Do large page allocations for the per cpu data. > > At which point we could grow the per cpu data by simply reallocating it on > each cpu and updating the register that holds the base pointer. If per cpu data areas have no fixed address then you cannot use list operations on per cpu data nor can the address of per cpu variables be stored anywhere. But maybe that is okay?