From owner-freebsd-hackers Sat Dec 8 3: 9:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from orange.csi.cam.ac.uk (orange.csi.cam.ac.uk [131.111.8.77]) by hub.freebsd.org (Postfix) with ESMTP id 87E9737B405 for ; Sat, 8 Dec 2001 03:09:13 -0800 (PST) Received: from dr263 (helo=localhost) by orange.csi.cam.ac.uk with local-esmtp (Exim 3.22 #1) id 16CfLv-0000CU-00; Sat, 08 Dec 2001 11:09:07 +0000 Date: Sat, 8 Dec 2001 11:09:07 +0000 (GMT) From: Dave Rufino X-X-Sender: To: Poul-Henning Kamp Cc: Terry Lambert , Alfred Perlstein , 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: > >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. Speaking for myself, first open and final close would be all I need for the nvidia driver - though i'm sure tracking dup/dup2/fcntl would be preferable in the general case. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message