From owner-freebsd-current  Tue Sep 12 15:49:17 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA06160
          for current-outgoing; Tue, 12 Sep 1995 15:49:17 -0700
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA06149
          for <current@FreeBSD.org>; Tue, 12 Sep 1995 15:49:09 -0700
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id PAA04509; Tue, 12 Sep 1995 15:48:47 -0700
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199509122248.PAA04509@GndRsh.aac.dev.com>
Subject: Re: Statistics request
To: terry@lambert.org (Terry Lambert)
Date: Tue, 12 Sep 1995 15:48:46 -0700 (PDT)
Cc: terry@lambert.org, current@FreeBSD.org
In-Reply-To: <199509122042.NAA02216@phaeton.artisoft.com> from "Terry Lambert" at Sep 12, 95 01:42:51 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1973      
Sender: current-owner@FreeBSD.org
Precedence: bulk

> 
> > Those are just spot selecting the non-0 ones...
> > 
> > Now fire up 3 copies of find:
> >         namei     2     1K      6K  8873K   168480    0     0  16,32,64,1K
> >         namei     2     1K      6K  8873K   172299    0     0  16,32,64,1K
> >         namei     1     1K      6K  8873K   172415    0     0  16,32,64,1K
> 
> The question is whether it self-zero's.  If it does, then care has been
> taken to doubly-break the buffer allocation code in nfs_namei(), which
> is what I'm trying to determine.

Note, I am running this on both client and server (infact every place but
the test bed right now is running this:)
FreeBSD GndRsh.aac.dev.com 2.1-STABLE FreeBSD 2.1-STABLE #1: Thu Sep  7 06:45:10  1995     root@burn4.aac.dev.com:/usr/src/sys/compile/GNDRSH  i386

> 
> I would expect that if this were the case, it would re-zero when idle.

While doing repeated captures to even get the above data most of the time
it reported 0. It hits the 2 or 1 about 1 in 20 hits of vmstat, this is
not a great way to collect data :-)

> If it is only singly broken, I'd expect the number of buffers to increase
> and keep increasing, or to start freeing stuff that isn't allocated.
> 
> I haven't determined what statistic free unallocated buffers would bump;
> unfortunately, I think it would be hidden in the noise on anything that
> could reproduce the error cases.
> 
> Garrett has reported 0's in the idle case on his box.
> 
> I will probably need to write some shell test cases to specifically
> exercise the bogus code.
> 
> Anyone have any idea what statistic will show preterbation when I free
> a buffer twice?  I'd like to watch that one too.
> 
> 
> 					Terry Lambert
> 					terry@lambert.org
> ---
> Any opinions in this posting are my own and not those of my present
> or previous employers.
> 


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD