Date: Sat, 08 Dec 2001 12:44:00 -0800 From: Mike Smith <msmith@freebsd.org> To: Terry Lambert <tlambert2@mindspring.com> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, Dave Rufino <dr263@hermes.cam.ac.uk>, Alfred Perlstein <bright@mu.org>, freebsd-hackers@FreeBSD.ORG Subject: Re: statefulness in character device drivers Message-ID: <200112082044.fB8Ki0T01241@mass.dis.org> In-Reply-To: Your message of "Sat, 08 Dec 2001 02:20:50 PST." <3C11E982.F50F2353@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >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).
I think this is the discriminating semantic that we've been missing out
on for a long time. We've always been so hung up on "per opener" data,
rather than "per open". Being able to return a handle from the device
open routine that's recoverable in read/write/strategy/close would be
*highly* desirable.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
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?200112082044.fB8Ki0T01241>