Date: Fri, 15 Dec 2006 16:42:17 -0500 From: Randall Stewart <rrs@cisco.com> To: Julian Elischer <julian@elischer.org> Cc: src-committers@FreeBSD.org, Andre Oppermann <andre@FreeBSD.org>, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org, Randall Stewart <rrs@FreeBSD.org>, "Bruce M. Simpson" <bms@FreeBSD.org> Subject: Re: cvs commit: src/lib/libc/net Makefile.inc sctp_sys_calls.c src/sys/sys param.h Message-ID: <458316B9.6090801@cisco.com> In-Reply-To: <4582FB5A.4010208@elischer.org> References: <200612151201.kBFC1qEv006825@repoman.freebsd.org> <4582A1E0.1050503@freebsd.org> <4582A6C9.8010009@FreeBSD.org> <4582FB5A.4010208@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote: > Bruce M. Simpson wrote: > >> Andre Oppermann wrote: >> >>> >>> What makes these sctp_* syscalls so special as opposed to their >>> generic and protocol agnostic counterparts? >> >> They're used for operations which do not have a direct correspondence >> in the existing functions, i.e. connecting to multihomed peers, and >> dealing with one-to-many sockets. >> >> See Section 9.3-9.12, UNIX Network Programming Vol 1 3e for more info. > > > > generally we would use socket ops or ioctls for this sort of thing.. > syscalls is not how they would normally be done.... > >> >> Regards, >> BMS > > Most of the things are NOT syscalls.. there are only a few for efficency.. the rest are a collection of socket options that perform the functions.. 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?458316B9.6090801>