From owner-cvs-all  Mon Oct  9  7:21:13 2000
Delivered-To: cvs-all@freebsd.org
Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147])
	by hub.freebsd.org (Postfix) with ESMTP
	id C257837B502; Mon,  9 Oct 2000 07:21:05 -0700 (PDT)
Received: from critter (localhost [127.0.0.1])
	by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e99EL2N65533;
	Mon, 9 Oct 2000 16:21:02 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: Re: cvs commit: src/sys/fs/devfs devfs_devs.c devfs_vfsops.c devfs_vnops.c 
In-Reply-To: Your message of "Mon, 09 Oct 2000 07:18:08 PDT."
             <200010091418.HAA78652@freefall.freebsd.org> 
Date: Mon, 09 Oct 2000 16:21:02 +0200
Message-ID: <65531.971101262@critter>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


>  Implement first cut try at killing cloned devices when they are
>  not needed anymore.  For now only the bpf driver is involved in
>  this experiment.  Cloned devices can set the SI_CHEAPCLONE flag
>  which allows us to destroy_dev() it when the vcount() drops to zero
>  and the vnode is reclaimed.  For now it's a requirement that the
>  driver doesn't keep persistent state from close to (re)open.

I'm kind of hessitant to add another function to the cdevsw[] to
handle device destruction, but if anybody can come up with a 
decent reason why a (cloning) pseudo driver would store persistent
data after last close, I'll reconsider.

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


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