From owner-cvs-src@FreeBSD.ORG Sat Dec 16 01:41:00 2006 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 29EF716A513; Sat, 16 Dec 2006 01:41:00 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from chipmunk.ai.net (axe.ai.net [205.134.161.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF34F43CAF; Sat, 16 Dec 2006 01:39:12 +0000 (GMT) (envelope-from trhodes@FreeBSD.org) Received: from localhost (net-ix.gw.ai.net [205.134.160.6] (may be forged)) by chipmunk.ai.net (8.13.4/8.13.4) with SMTP id kBG1f73S062998; Fri, 15 Dec 2006 20:41:07 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Fri, 15 Dec 2006 20:40:44 -0500 From: Tom Rhodes To: John Baldwin Message-Id: <20061215204044.22d7d0e7.trhodes@FreeBSD.org> In-Reply-To: <200612151551.31355.jhb@freebsd.org> References: <200612151201.kBFC1qEv006825@repoman.freebsd.org> <4582A6C9.8010009@FreeBSD.org> <4582FB5A.4010208@elischer.org> <200612151551.31355.jhb@freebsd.org> Organization: The FreeBSD Project X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: src-committers@FreeBSD.org, andre@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org, rrs@FreeBSD.org, julian@elischer.org, bms@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/net Makefile.inc sctp_sys_calls.c src/sys/sys param.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Dec 2006 01:41:00 -0000 On Fri, 15 Dec 2006 15:51:30 -0500 John Baldwin wrote: > On Friday 15 December 2006 14:45, 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.... > > I'll give a free paper cookie to the first person to actually go _read_ the > committed code and notice that, *tada*, aside from the sctp_send*(), and > sctp_recvmsg() functions, these are indeed library wrapper functions around > getsockopt() and setsockopt(). > Adding useless fodder, I must say ... "John for the win" -- Tom Rhodes