Date: Fri, 24 Feb 2006 04:14:35 -0800
From: Andrew Morton <akpm@osdl.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: bfink@eventmonitor.com, linux-kernel@vger.kernel.org
Subject: Re: NFS Still broken in 2.6.x?
Message-Id: <20060224041435.733b4f0d.akpm@osdl.org>
In-Reply-To: <1140734824.7963.38.camel@lade.trondhjem.org>
References: <43FE1CAD.3050806@eventmonitor.com>
	<1140734824.7963.38.camel@lade.trondhjem.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 995
Lines: 21

Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
>
> On Thu, 2006-02-23 at 15:35 -0500, Bryan Fink wrote:
>  > Hi All.  I'm running into a bit of trouble with NFS on 2.6.  I see that
>  > at least Trond thought, mid-January, that "The readahead algorithm has
>  > been broken in 2.6.x for at least the past 6 months." (
>  > http://www.ussg.iu.edu/hypermail/linux/kernel/0601.2/0559.html) Anyone
>  > know if that has been fixed?
> 
>  No it hasn't been fixed. ...and no, this is not a problem that only
>  affects NFS: it just happens to give a more noticeable performance
>  impact due to the larger latency of NFS over a 100Mbps link.

iirc, last time we went round this loop Ram and I were unable to reproduce it.

Does anyone have a testcase?
-
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/