From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754935AbXDZTXE (ORCPT ); Thu, 26 Apr 2007 15:23:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754941AbXDZTXE (ORCPT ); Thu, 26 Apr 2007 15:23:04 -0400 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:40143 "EHLO ebiederm.dsl.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754935AbXDZTXB (ORCPT ); Thu, 26 Apr 2007 15:23:01 -0400 From: ebiederm@xmission.com (Eric W. Biederman) To: Christoph Lameter Cc: David Chinner , Nick Piggin , linux-kernel@vger.kernel.org, Mel Gorman , William Lee Irwin III , Jens Axboe , Badari Pulavarty , Maxim Levitsky Subject: Re: [00/17] Large Blocksize Support V3 References: <20070424222105.883597089@sgi.com> <46303A98.9000605@yahoo.com.au> <20070426063830.GE32602149@melbourne.sgi.com> Date: Thu, 26 Apr 2007 13:21:50 -0600 In-Reply-To: (Christoph Lameter's message of "Thu, 26 Apr 2007 11:59:43 -0700 (PDT)") Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) 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 Christoph Lameter writes: > On Thu, 26 Apr 2007, Eric W. Biederman wrote: > >> If you can make small things go fast, everything speeds up. >> If you can only make big things go fast only some things speed up. >> >> I want to make small things go fast so everything speeds up. > > A reductionist operating system theory? Have you ever heard of emergent > properties? A system comprised of pieces can as a whole exibit other > characteristics than the basic elements would provide. > > I think it is wrong to use the same small things for big things. You > would not tow a tanker with your bicycle. Similarly you could use small > pages for text files but huge page sizes when you need to transfer > gigabytes or terabytes of memory. Its wrong to dictate ones size fits > all. (Memories of my relatives in the eastern bloc surface but I better shut > up.) Think of it like designing a cpu. Which would you rather have a faster clock rate or a new instruction say floating point multiply-accumulate that means you theoretically double your floating point computation speed at a cost of reducing your clock rate? Up to the limit of it being possible you get more bang out of improving the little things. CPUs unfortunately pretty much hit the limit of improving clock rates. I don't think we are at the limit of making small things like syscalls, and pages go fast. Eric