Anders Persson writes: > > - 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.
What's the rationale for function-per-ioctl rather than just having ksock_ioctl() and (if necessary) ksock_fcntl()? -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
