Re: statefulness in character device drivers

On Sat, 8 Dec 2001, Alfred Perlstein wrote: > * Robert Watson <[EMAIL PROTECTED]> [011208 19:43] wrote: > > > > I had some patches to do this, but lost them ages ago. If I get really > > bored next week, I'll redo them and stick them in a perforce branch. That > > said, it requires a bit more

Re: statefulness in character device drivers

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).

Re: statefulness in character device drivers

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", "som

Re: statefulness in character device drivers

On Fri, 7 Dec 2001, Alfred Perlstein wrote: > * Poul-Henning Kamp <[EMAIL PROTECTED]> [011207 07:57] wrote: > > In message <[EMAIL PROTECTED]>, Dave R > > ufino writes: > > >Hi, > > > > > >I remember some discussions a while ago about adding statefulness to > > >the character device driver laye

statefulness in character device drivers

Hi, I remember some discussions a while ago about adding statefulness to the character device driver layer. What's the consensus now ? Is it going to be added, and if so, when ? Thanks, David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the m