Jeremy,
Sorry about the late reply, somehow the mail slipped pass me. My
comments are inline.
Jeremy Harris wrote:
Anders Persson wrote:
http://www.opensolaris.org/os/project/kernel-sockets/files/kernel-sockets.pdf
Overall, good. Two points:
- I'd have been tempted to stick with a synchronous interface for the
initial development; lose the event notification. Is there significant
demand from potential customers, which wouldn't be satisfied by them
creating threads?
Yes, people have expressed interested in having an asynchronous
notification system. However, a synchronous interface is definitely more
familiar to use, but that such an interface could always be built on top
of the current interface.
- Special-casing nonblocking mode seems odd. Are no other ioctls
relevant?
SIOCATMARK? FIONREAD?
In the current design, all ioctls that affect sockets would be
represented explicitly by a function. SIOCATMARK is handled
(ksock_atmark()); I mention it in the text, but I seems like I forgot to
add it to the function listing. However, I completely forgot about
FIONREAD, and a function would have to be added to handle it.
Cheers,
Jeremy Harris
Thank you very much for you comments.
Anders
_______________________________________________
networking-discuss mailing list
[email protected]
