From owner-freebsd-arch@FreeBSD.ORG  Fri May  5 09:06:46 2006
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
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 1622A16A400;
	Fri,  5 May 2006 09:06:46 +0000 (UTC)
	(envelope-from maxim@macomnet.ru)
Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3538B43D5E;
	Fri,  5 May 2006 09:06:44 +0000 (GMT)
	(envelope-from maxim@macomnet.ru)
Received: from localhost (localhost [127.0.0.1])
	by mp2.macomnet.net (8.13.4/8.13.3) with ESMTP id k4596h23056931;
	Fri, 5 May 2006 13:06:43 +0400 (MSD)
	(envelope-from maxim@macomnet.ru)
Date: Fri, 5 May 2006 13:06:43 +0400 (MSD)
From: Maxim Konovalov <maxim@macomnet.ru>
To: Mario Sergio Fujikawa Ferreira <lioux@freebsd.org>
In-Reply-To: <20060505033749.76815.qmail@exxodus.fedaykin.here>
Message-ID: <20060505125901.H56755@mp2.macomnet.net>
References: <20060505033749.76815.qmail@exxodus.fedaykin.here>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: 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 <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 May 2006 09:06:46 -0000

Hello,

On Fri, 5 May 2006, 00:37-0300, Mario Sergio Fujikawa Ferreira wrote:

> Hi,
>
> 	I would like to propose a new socket option: SO_DONTFRAGMENT
> on the lines of IP_DONTFRAG.
[...]

According to ip(4) and rev. 1.247 ip_output.c commit log IP_DONTFRAG
should work for IP and UPD.  I'm not sure we need to invent new
setsockopt() option just for TCP.  Perhaps extending IP_DONTFRAG for
TCP is better idea.  Anyhow, ask Andre.

-- 
Maxim Konovalov