From owner-freebsd-hackers Sat Dec 8 17:40:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id DE65D37B41B for ; Sat, 8 Dec 2001 17:40:45 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fB91eFi77037; Sat, 8 Dec 2001 20:40:15 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sat, 8 Dec 2001 20:40:15 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp Cc: Terry Lambert , Dave Rufino , Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: statefulness in character device drivers In-Reply-To: <47779.1007808692@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 8 Dec 2001, Poul-Henning Kamp wrote: > >> The issue is non-trivial to fix because we currently don't pass > >> dup(2) events through the vnode layer. > > > >Are you sure this is even necessary? > > > >They are talking about "per-open", not "per-fd-instance" data, > >which could easily exclude dup, dup2, and fcntl(f_DUPFD). > > If you don't include dup/dup2/fnctl in your accounting, you can only > reliably tell "first open", "another open", "some close" and "final > close". You an modulate this with the pid, but you still have no idea > what is going on in any amount of detail. Generally speaking, the information of interest to me would be "first open" for a particular struct file, and "last close". Other migration of the reference to struct file around the system would not be so useful: if a process wants new references to be visible at the device layer, they can always open more references using new struct files. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message