From owner-cvs-src@FreeBSD.ORG Fri Dec 15 21:23:28 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 29D6B16A64F for ; Fri, 15 Dec 2006 21:23:28 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outV.internet-mail-service.net (outV.internet-mail-service.net [216.240.47.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97F4C43CC0 for ; Fri, 15 Dec 2006 21:21:40 +0000 (GMT) (envelope-from julian@elischer.org) Received: from shell.idiom.com (HELO idiom.com) (216.240.47.20) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Fri, 15 Dec 2006 13:08:06 -0800 Received: from [10.251.18.229] (nat.ironport.com [63.251.108.100]) by idiom.com (8.12.11/8.12.11) with ESMTP id kBFLNKvJ085694; Fri, 15 Dec 2006 13:23:21 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <45831241.6010007@elischer.org> Date: Fri, 15 Dec 2006 13:23:13 -0800 From: Julian Elischer User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025) MIME-Version: 1.0 To: John Baldwin References: <200612151201.kBFC1qEv006825@repoman.freebsd.org> <4582A6C9.8010009@FreeBSD.org> <4582FB5A.4010208@elischer.org> <200612151551.31355.jhb@freebsd.org> In-Reply-To: <200612151551.31355.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: src-committers@freebsd.org, Andre Oppermann , cvs-src@freebsd.org, cvs-all@freebsd.org, Randall Stewart , "Bruce M. Simpson" 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: Fri, 15 Dec 2006 21:23:28 -0000 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(). > *blush* it was the fact that they SAID they were syscalls that tripped me up. I'll go shut up now..