From owner-cvs-all  Sun Mar 17 21:39:13 2002
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0D0FF37B404; Sun, 17 Mar 2002 21:39:05 -0800 (PST)
Received: (from mckusick@localhost)
	by freefall.freebsd.org (8.11.6/8.11.6) id g2I5d5351291;
	Sun, 17 Mar 2002 21:39:05 -0800 (PST)
	(envelope-from mckusick)
Message-Id: <200203180539.g2I5d5351291@freefall.freebsd.org>
From: Kirk McKusick <mckusick@FreeBSD.org>
Date: Sun, 17 Mar 2002 21:39:04 -0800 (PST)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/sys/fs/nullfs null_vnops.c
X-FreeBSD-CVS-Branch: HEAD
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
List-ID: <cvs-all.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

mckusick    2002/03/17 21:39:04 PST

  Modified files:
    sys/fs/nullfs        null_vnops.c 
  Log:
  Cannot release vnode underlying the nullfs vnode in null_inactive
  as it leaves the nullfs vnode allocated, but with no identity. The
  effect is that a null mount can slowly accumulate all the vnodes
  in the system, reclaiming them only when it is unmounted. Thus
  the null_inactive state instead accelerates the release of the
  null vnode by calling vrecycle which will in turn call the
  null_reclaim operator. The null_reclaim routine then does the
  freeing actions previosuly (incorrectly) done in null_inactive.
  
  Revision  Changes    Path
  1.51      +27 -20    src/sys/fs/nullfs/null_vnops.c

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message