From owner-freebsd-net@FreeBSD.ORG Tue Jan 20 12:53:02 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FD0C16A4CE; Tue, 20 Jan 2004 12:53:02 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D6AB43D6B; Tue, 20 Jan 2004 12:52:33 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i0KKqW5P016692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jan 2004 15:52:32 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i0KKqRq5098009; Tue, 20 Jan 2004 15:52:27 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16397.38155.418523.634400@grasshopper.cs.duke.edu> Date: Tue, 20 Jan 2004 15:52:27 -0500 (EST) To: Andre Oppermann In-Reply-To: <400D9271.1259CBC8@freebsd.org> References: <16397.36782.415899.626311@grasshopper.cs.duke.edu> <400D9271.1259CBC8@freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: freebsd-net@freebsd.org Subject: Re: tcp mss MCLBYTES restriction X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 20:53:02 -0000 Andre Oppermann writes: > When I was implementing the tcp_hostcache I reorganized/redid the > tcp_mss() function and wondered about that too. I don't know if > this rounding to MCLBYTES is still the right thing to do. I have the feeling its something from ancient days on vaxes. ;) > > Would it be OK if I made this code optional via a sysctl? > > Could you run some bechmarks with the current MCLBYTES rounding > and without it on 100Mbit 1.5kMTU and GigE with 9k MTU? 1.5k MTU won't matter -- it doesn't hit the rounding case anyway. But I can certainly run some tests with 9k. Drew