Date: Fri, 15 Dec 2006 16:39:10 -0500 From: Randall Stewart <rrs@cisco.com> To: Andre Oppermann <andre@freebsd.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/lib/libc/net Makefile.inc sctp_sys_calls.c src/sys/sys param.h Message-ID: <458315FE.6080408@cisco.com> In-Reply-To: <4582A1E0.1050503@freebsd.org> References: <200612151201.kBFC1qEv006825@repoman.freebsd.org> <4582A1E0.1050503@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Andre Oppermann wrote: > Randall Stewart wrote: > >> rrs 2006-12-15 12:01:50 UTC >> >> FreeBSD src repository >> >> Modified files: >> lib/libc/net Makefile.inc sys/sys param.h >> Added files: >> lib/libc/net sctp_sys_calls.c Log: >> This adds the "system calls" >> sctp_connectx() >> sctp_bindx() >> sctp_sendmsg() >> sctp_send() >> sctp_sendx() >> sctp_sendmsgx() >> sctp_recvmsg() > > > What makes these sctp_* syscalls so special as opposed to their > generic and protocol agnostic counterparts? > The generic counter parts are what these calls (at least a few of them send/recv etc) use to actually make the call. You can use either the "generic" ones.. which of course is more efficent. Or you can use the sctp_send* or sctp_recv* call instead.. which is more portable.. since they conform to the socket api document. Some of these (the rest) are not even system calls. but a collection of socket options.. I have just got through getting the first cut of all the man pages together... sigh.. still need more work on sctp(4).. but I think I will send it all to George for approval.. I have also asked some of the other SCTP team members to have a look at the man pages and see if I missed anything .. which I probably did :-) R -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 <or> 803-317-4952 (cell)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?458315FE.6080408>