From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 09:26:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28FDB16A4CE; Tue, 9 Mar 2004 09:26:59 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DC8943D2D; Tue, 9 Mar 2004 09:26:59 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.3) with ESMTP id i29HQsRH005490; Tue, 9 Mar 2004 09:26:54 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i29HQr8S005489; Tue, 9 Mar 2004 09:26:53 -0800 Date: Tue, 9 Mar 2004 09:26:53 -0800 From: Brooks Davis To: Mike Silbersack Message-ID: <20040309172653.GC19707@Odin.AC.HMC.Edu> References: <404BA723.C8141806@freebsd.org> <20040308182431.4FA6D5D08@ptavv.es.net> <20040308202210.GB485@Odin.AC.HMC.Edu> <20040309031549.L49735@odysseus.silby.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="H8ygTp4AXg6deix2" Content-Disposition: inline In-Reply-To: <20040309031549.L49735@odysseus.silby.com> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: Andre Oppermann cc: freebsd-net@freebsd.org cc: David Malone cc: freebsd-current@freebsd.org Subject: Re: My planned work on networking stack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Mar 2004 17:26:59 -0000 --H8ygTp4AXg6deix2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 09, 2004 at 03:19:58AM -0600, Mike Silbersack wrote: >=20 > On Mon, 8 Mar 2004, Brooks Davis wrote: >=20 > > I've got a co-worker who is part of a research group at ISI that > > is doing research on long fat pipes with large streams. They are > > intrested in doing a SACK implementation. I hope to have some more > > information later this week. > > > > -- Brooks >=20 > In order to make SACK easier to digest, perhaps it should be suggested > that SACK be implemented in stages: >=20 > 1. Internal structures are updated to handle SACK, and the stack handles > the receive side of SACK properly. (The stack advertises itself as SACK > capable, of course.) >=20 > 2. The transmit side of SACK is implemented. >=20 > >From what I recall about SACK, the implementation of part 1 would be > straightforward to verify and therefore easy to integrate. The send side > would, of course, require more attention, and it would be more likely to > get it if it could be reviewed seperately. We'll definatly keep this in mind. Thanks. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --H8ygTp4AXg6deix2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFATf5bXY6L6fI4GtQRAnTvAJ9/7q/2Arn9VZheQLJZ90nTY+a+qgCgs2AH IlpKONSo7H5ejqM6n0d+8ro= =75Ly -----END PGP SIGNATURE----- --H8ygTp4AXg6deix2--