Subject: Re: NFS and kernel 2.6.x
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Charles Shannon Hendrix <shannon@widomaker.com>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <20040417000353.GA3750@widomaker.com>
References: <20040416011401.GD18329@widomaker.com>
	 <1082079061.7141.85.camel@lade.trondhjem.org>
	 <20040416190126.GB408@widomaker.com>
	 <1082144608.2581.156.camel@lade.trondhjem.org>
	 <20040417000353.GA3750@widomaker.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1082179726.3012.7.camel@lade.trondhjem.org>
Mime-Version: 1.0
Date: Fri, 16 Apr 2004 22:28:47 -0700
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 977
Lines: 24

On Fri, 2004-04-16 at 17:03, Charles Shannon Hendrix wrote:
> > 
> > 2.6.x can cache a lot more data, and will tend to write it out in a more
> > lazy fashion (i.e. only when the user requests it). That means the
> > writes tend to occur in a more bursty fashion.
> 
> That makes sense.
> 
> Was there a specific reason for making NFS traffic bursty, or did it
> just work out that way?

It's an inevitable side-effect of the increased caching. If you are
constantly writing out data, then you spread out the load a lot more
than if you wait until the user actually requests a flush.
On the other hand, it means that if your application reads/writs several
times over the same page, then you only write it out once.

Cheers,
  Trond
-
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/