From owner-freebsd-arch@FreeBSD.ORG Wed May 10 19:23:20 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C80616A45E; Wed, 10 May 2006 19:23:20 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout3.yahoo.com (mrout3.yahoo.com [216.145.54.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B7E143D6B; Wed, 10 May 2006 19:23:17 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.lan.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout3.yahoo.com (8.13.6/8.13.4/y.out) with ESMTP id k4AJLg4x012936; Wed, 10 May 2006 12:21:43 -0700 (PDT) Date: Wed, 10 May 2006 15:21:41 -0400 Message-ID: From: gnn@freebsd.org To: Mario Sergio Fujikawa Ferreira In-Reply-To: <20060509231911.54375.qmail@exxodus.fedaykin.here> References: <20060505033749.76815.qmail@exxodus.fedaykin.here> <20060505192943.Q17611@fledge.watson.org> <20060509231911.54375.qmail@exxodus.fedaykin.here> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: Robert Watson , freebsd-arch@freebsd.org Subject: Re: RFC {get,set}socktopt SO_DONTFRAGMENT X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 May 2006 19:23:25 -0000 At Tue, 9 May 2006 20:18:48 -0300, Mario Sergio Fujikawa Ferreira wrote: > I was thinking of a blanket option that would cover anything > a socket could have instead of having options inside "every" single > place. > > Of couse, IP_DONTFRAG applies very well in most situations. > However, I don't think that SO_DONTFRAGMENT would be a replacement > but rather a more "generic" option. > > Well, I could just be missing something and saying something > naive. :) So I apologize if I am missing something obvious. > No apology necessary. I think that a generic option would be too misleading. Those who want to say "Don't Fragment" usually are specialists and we dont' want people accidentally pessimizing their applications by setting this when they don't mean to. Best, George