From owner-cvs-all@FreeBSD.ORG Fri Dec 15 13:57:39 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 F16F916A540; Fri, 15 Dec 2006 13:57:38 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 240B043D70; Fri, 15 Dec 2006 13:55:23 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id kBFDv4E4065317; Fri, 15 Dec 2006 05:57:04 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id kBFDv4W4065316; Fri, 15 Dec 2006 05:57:04 -0800 (PST) (envelope-from rizzo) Date: Fri, 15 Dec 2006 05:57:04 -0800 From: Luigi Rizzo To: "Bruce M. Simpson" Message-ID: <20061215055704.A65183@xorpc.icir.org> References: <200612151201.kBFC1qEv006825@repoman.freebsd.org> <4582A1E0.1050503@freebsd.org> <4582A6C9.8010009@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <4582A6C9.8010009@FreeBSD.org>; from bms@FreeBSD.org on Fri, Dec 15, 2006 at 01:44:41PM +0000 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 13:57:39 -0000 On Fri, Dec 15, 2006 at 01:44:41PM +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. i think Andre's question was this: normally we use {set|get}sockopt() to configure the socket as desired for special features (e.g. multicast is one). Why is it undesirable to use the same kind of overloading for sctp ? cheers luigi