From owner-freebsd-net@FreeBSD.ORG Mon Dec 13 21:48:41 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 A85E716A4CE; Mon, 13 Dec 2004 21:48:41 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06A9343D73; Mon, 13 Dec 2004 21:48:40 +0000 (GMT) (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.13.1/8.13.1) with ESMTP id iBDLmeA4027513 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Dec 2004 16:48:40 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id iBDLmZwV054857; Mon, 13 Dec 2004 16:48:35 -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: <16830.3635.392271.923345@grasshopper.cs.duke.edu> Date: Mon, 13 Dec 2004 16:48:35 -0500 (EST) To: Andre Oppermann In-Reply-To: <41BE0ADA.9A1EE748@freebsd.org> References: <41BA0088.9000107@freebsd.org> <41BDD1C7.7060105@freebsd.org> <16830.1004.797220.47672@grasshopper.cs.duke.edu> <41BE0ADA.9A1EE748@freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: freebsd-net@freebsd.org Subject: Re: Rewritten TCP reassembly 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: Mon, 13 Dec 2004 21:48:42 -0000 Andre Oppermann writes: > > I have already the next round in the works which is optimized even more > by merging consecutive mbuf chains together (at the moment I have packet > segment chains which have a direct pointer to the mbuf at the end of the > chain) and which get passed in one go to soappend_stream. This removes > the "present" loop and simplifies the general code a bit more again. Great.. I've been a little busy, and have only run tests -- I haven't even looked at the code ;) > With this and two other optimizations I have in mind you should be able > to get very close to the theoretical maximum bandwidth of your current > 4Gig Myrinet cards. > > There are a couple of other TCP tweaks that would help your special case > some more now though. FWIW, the out-of-order frames are a firmware bug that we hope to fix soon. Its just icing on the cake that the bug makes such a nice test case for you ;) With no copy overhead (kttcp), 3.95Gb/sec is easily achievable, even in 5-stable with the old TCP reassembly code. Drew