Darren Reed writes:
> To follow up on my earlier post...
> I've put a bit more thought into it...
> The impetus for doing this is BPF. BPF keeps per
> open file data for each file descriptor.

I'd suggest driver-disc...@openopensolaris.org in addition to (or
instead of) opensolaris-code.

> To meet these requirements, this proposal suggests two new
> functions: ddi_minor_alloc and ddi_minor_free.

What's wrong with the existing id_alloc() function?

> Each of the following entry points into the driver will be
> supplied with a new, extra, paramter: aread, awrite, chpoll,
> dump, ioctl, mmap, print, read, segmap, strategy and write.
> close is supplied pointer to the context pointer, which the

And for this part, why are the ddi_soft_state(9F) functions not
sufficient?

-- 
James Carlson, Solaris Networking              <james.d.carl...@sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to