In message <[EMAIL PROTECTED]>, Terry Lambert writes: >Poul-Henning Kamp wrote: >> >> Most likely he means a per-open(2) opaque datum that is kept in >> >> struct file and passed to the underlying routines. >> > >> >Sorry, unbelievably bad at explaining myself. Per-open data is what i >> >meant. The reason I'm interested is it would make a full nvidia driver >> >port quite a bit easier. >> >> Sorry, I know of no current plans which adress this. >> >> 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. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | 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 [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
