On Fri, 15 Dec 2006, Randall Stewart wrote:
There are only 4 new system calls..
a) sctp_generic_sendmsg()
b) sctp_generic_sendmsg_iov()
c) sctp_generic_recvmsg()
d) sctp_peeloff()
Peeloff is a lot like accept() .. it returns a new socket. It could be move
to a socket option petty easily.. Michael Tuexen already did one for Apple
:-)
I'd really rather we didn't try to fit these sorts of things into socket
options myself: the current blend of system calls and socket options for the
new interfaces appears right to me. Especially with respect to in-kernel
consumers of socket interfaces, having the socket option code make assumptions
about file descriptor arrays on the current process, etc, would not be the
right thing. Socket options work well for simple get/set interfaces, but
going too much further is just asking for trouble. It also makes handling
issues like binary compatibility for ABI changes a lot more tricky: we have a
mature mechanism for handling versioning of system calls, but not for socket
options.
Robert N M Watson
Computer Laboratory
University of Cambridge
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
