From owner-cvs-all@FreeBSD.ORG Fri Dec 15 19:45:58 2006 Return-Path: X-Original-To: cvs-all@FreeBSD.org Delivered-To: cvs-all@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 934F916A47E for ; Fri, 15 Dec 2006 19:45:58 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outC.internet-mail-service.net (outC.internet-mail-service.net [216.240.47.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C52743CBF for ; Fri, 15 Dec 2006 19:44:10 +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 11:30:37 -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 kBFJjjwK036441; Fri, 15 Dec 2006 11:45:46 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <4582FB5A.4010208@elischer.org> Date: Fri, 15 Dec 2006 11:45:30 -0800 From: Julian Elischer User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025) MIME-Version: 1.0 To: "Bruce M. Simpson" References: <200612151201.kBFC1qEv006825@repoman.freebsd.org> <4582A1E0.1050503@freebsd.org> <4582A6C9.8010009@FreeBSD.org> In-Reply-To: <4582A6C9.8010009@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Randall Stewart , src-committers@FreeBSD.org, Andre Oppermann , cvs-all@FreeBSD.org, cvs-src@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/net Makefile.inc sctp_sys_calls.c src/sys/sys param.h X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Dec 2006 19:45:58 -0000 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