From owner-freebsd-current  Sat Jul 19 02:22:25 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id CAA15635
          for current-outgoing; Sat, 19 Jul 1997 02:22:25 -0700 (PDT)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA15630
          for <current@freebsd.org>; Sat, 19 Jul 1997 02:22:19 -0700 (PDT)
Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2])
	by nlsystems.com (8.8.5/8.8.5) with SMTP id KAA15568;
	Sat, 19 Jul 1997 10:22:28 +0100 (BST)
Date: Sat, 19 Jul 1997 10:22:28 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Jaye Mathisen <mrcpu@cdsnet.net>
cc: current@freebsd.org
Subject: Re: nfsiod in 3.0-current oddity/broke.
In-Reply-To: <Pine.NEB.3.95.970718161822.26098F-100000@mail.cdsnet.net>
Message-ID: <Pine.BSF.3.95q.970719102055.445K-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 18 Jul 1997, Jaye Mathisen wrote:

> 
> 
> On my 2.2.2 box, my nfsiod's (12) of them, all got a little bit of CPU
> time under heavye load.
> 
> After upgrading to 3.0, none of them except the first one get any time.
> 
> Seems broke.

Is the performance any different though?  The NFS in 2.2.2 and 3.0 are
very similar.  In particular, there is no difference in the code for
scheduling iods.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 951 1891
					Fax:   +44 181 381 1039