From owner-freebsd-hackers  Sun Aug 20 00:26:19 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id AAA14756
          for hackers-outgoing; Sun, 20 Aug 1995 00:26:19 -0700
Received: from sunny.bog.msu.su (sunny.bog.msu.su [158.250.20.1])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id AAA14748
          for <hackers@freefall.freebsd.org>; Sun, 20 Aug 1995 00:26:14 -0700
Received: (from dima@localhost) by sunny.bog.msu.su (8.6.12/8.6.12) id LAA00806; Sun, 20 Aug 1995 11:23:00 +0400
Date: Sun, 20 Aug 1995 11:22:59 +0400 (????)
From: Dmitry Khrustalev <dima@bog.msu.su>
To: David Greenman <davidg@Root.COM>
cc: hackers@freefall.freebsd.org
Subject: Re: Making a FreeBSD NFS server 
In-Reply-To: <199508200552.WAA00268@corbin.Root.COM>
Message-ID: <Pine.SOL.3.91.950820111605.552D-100000@sunny.bog.msu.su>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: hackers-owner@FreeBSD.org
Precedence: bulk


On Sat, 19 Aug 1995, David Greenman wrote:

> >> 
> >> >     What can I do to improve NFS writes to a FreeBSD server?  The
> >> > machine was idle at the time, with four nfsd's running.  Should I be
> >> > using UDP or TCP (I turned both on)?
> >> 
> >
> >Assuming you are running 2.1 branch: current (2.2) code includes support 
> >for write gathering, which can improve large write performance.
> >Be warned: 2.2 kernel is incompatible with 2.1 user space utilities.
> 
>    If there is interest, I'll implement an NFS_ASYNC kernel option for both
> FreeBSD 2.1 and 2.2.

Kernel option or per filesystem option? Switching it on for all 
filesystems at once is evil. And if nfs3 data corruption problems are 
resolved, this option will not have any real value.

-Dima

> 
> -DG
>