From owner-freebsd-hackers Sat Dec 8 3:35:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 76C8837B420 for ; Sat, 8 Dec 2001 03:35:15 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fB8BXgj49039; Sat, 8 Dec 2001 12:33:42 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Dave Rufino Cc: Terry Lambert , Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: statefulness in character device drivers In-Reply-To: Your message of "Sat, 08 Dec 2001 11:09:07 GMT." Date: Sat, 08 Dec 2001 12:33:41 +0100 Message-ID: <49036.1007811221@critter.freebsd.dk> From: Poul-Henning Kamp 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 In message , Dav e Rufino writes: > > >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. first open/last close has been the UNIX way for decades... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | 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 freebsd-hackers" in the body of the message