Date: Sat, 08 Dec 2001 12:33:41 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Dave Rufino <dr263@hermes.cam.ac.uk> Cc: Terry Lambert <tlambert2@mindspring.com>, Alfred Perlstein <bright@mu.org>, freebsd-hackers@FreeBSD.ORG Subject: Re: statefulness in character device drivers Message-ID: <49036.1007811221@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 08 Dec 2001 11:09:07 GMT." <Pine.SOL.4.33.0112081058220.29494-100000@orange.csi.cam.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.SOL.4.33.0112081058220.29494-100000@orange.csi.cam.ac.uk>, 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49036.1007811221>