From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754829AbXDZP7M (ORCPT ); Thu, 26 Apr 2007 11:59:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754830AbXDZP7M (ORCPT ); Thu, 26 Apr 2007 11:59:12 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:37292 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754829AbXDZP7J (ORCPT ); Thu, 26 Apr 2007 11:59:09 -0400 Date: Thu, 26 Apr 2007 16:58:55 +0100 From: Christoph Hellwig To: Nick Piggin Cc: "Eric W. Biederman" , Christoph Lameter , linux-kernel@vger.kernel.org, Mel Gorman , William Lee Irwin III , David Chinner , Jens Axboe , Badari Pulavarty , Maxim Levitsky Subject: Re: [00/17] Large Blocksize Support V3 Message-ID: <20070426155855.GA16337@infradead.org> Mail-Followup-To: Christoph Hellwig , Nick Piggin , "Eric W. Biederman" , Christoph Lameter , linux-kernel@vger.kernel.org, Mel Gorman , William Lee Irwin III , David Chinner , Jens Axboe , Badari Pulavarty , Maxim Levitsky References: <20070424222105.883597089@sgi.com> <463048FE.5000600@yahoo.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <463048FE.5000600@yahoo.com.au> User-Agent: Mutt/1.4.2.2i X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 26, 2007 at 04:38:54PM +1000, Nick Piggin wrote: > Hardware is built to handle many small pages efficintly, and I don't > understand how it could be an SGI-only issue. Sure, you may have an > order of magnitude or more memory than anyone else, but even my lowly > desktop _already_ has orders of magnitude more pages than it has TLB > entries or cache -- if a workload is cache-nice for me, it probably > will be on a 1TB machine as well, and if it is bad for the 1TB machine, > it is also bad on mine. It's not an SGI-only issue, but apparently SGI are the only ones that actually care about real highend linux setups to work on these issues. The Problem is not on the CPU hardware side. It's on the Software side and Storage hardware side, or rather a combination of the two.