From: Andrew Morton Subject: Re: 2.6.30-rc deadline scheduler performance regression for iozone over NFS Date: Wed, 13 May 2009 09:32:29 -0700 Message-ID: <20090513093229.097b47d2.akpm@linux-foundation.org> References: <20090508120119.8c93cfd7.akpm@linux-foundation.org> <20090511081415.GL4694@kernel.dk> <20090511165826.GG4694@kernel.dk> <20090512204433.7eb69075.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: Jeff Moyer , Jens Axboe , linux-kernel@vger.kernel.org, "Rafael J. Wysocki" , "J. Bruce Fields" , Jim Rees , linux-nfs@vger.kernel.org To: Olga Kornievskaia Return-path: Received: from smtp1.linux-foundation.org ([140.211.169.13]:37447 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752003AbZEMQmK (ORCPT ); Wed, 13 May 2009 12:42:10 -0400 In-Reply-To: Sender: linux-nfs-owner@vger.kernel.org List-ID: On Wed, 13 May 2009 12:20:57 -0400 Olga Kornievskaia wrote: > I believe what you are seeing is how well TCP autotuning performs. > What old NFS code was doing is disabling autotuning and instead using > #nfsd thread to scale TCP recv window. You are providing an example of > where setting TCP buffer sizes outperforms TCP autotuning. While this > is a valid example, there is also an alternative example of where old > NFS design hurts performance. Jeff's computer got slower. Can we fix that?