On Sat, 8 Dec 2001, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, 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...
Oops, I meant it shouldn't be necessary to be notified of dup()ed fds
in the device driver, which is probably not what you were driving at
anyway :/
David
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
