* Poul-Henning Kamp <email@example.com> [011208 05:35] wrote:
> In message <Pine.SOL.firstname.lastname@example.org>, 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...
Yes, but afaik without a way to differenciate between two
opens. Being able to notice whether a file is being operated
on via which open is the important part.
This would probably involve changing VOP_OPENs to pass a void **
that would be stored in the struct file that would be passed
to subsequent ioctl/read/write/close operations.
-Alfred Perlstein [email@example.com]
'Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.'
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message