From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 13:42:06 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 195AA16A4CE; Tue, 9 Mar 2004 13:42:06 -0800 (PST) Received: from postal2.es.net (proxy.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07B5243D1D; Tue, 9 Mar 2004 13:42:06 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Tue, 09 Mar 2004 13:42:05 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 3EE2D5D07; Tue, 9 Mar 2004 13:42:05 -0800 (PST) To: Brad Knowles In-reply-to: Your message of "Tue, 09 Mar 2004 20:13:11 +0100." Date: Tue, 09 Mar 2004 13:42:05 -0800 From: "Kevin Oberman" Message-Id: <20040309214205.3EE2D5D07@ptavv.es.net> cc: freebsd-net@freebsd.org cc: Jeffrey Hsu cc: freebsd-current@freebsd.org Subject: Re: Who wants SACK? (Re: was 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 21:42:06 -0000 > Date: Tue, 9 Mar 2004 20:13:11 +0100 > From: Brad Knowles > Sender: owner-freebsd-current@freebsd.org > > At 3:32 PM -0800 2004/03/08, Jeffrey Hsu wrote: > > > What Luigi says is absolutely correct. It doesn't take a lot to > > get this done. I've talked to a number of companies about implementing > > SACK for them and while there was interest, no one wanted to fund > > it all themselves, potentially for the benefit of their competitors. > > Out of curiosity, can someone provide some pointers as to where > SACK really helps? Is this just for high-speed WANs and doesn't help > on LANs, or is it useful in both contexts? Also, at what > speeds/packet sizes does SACK start to become really useful? > > I'm just wondering if there aren't a lot of people who could > benefit from something like this, only they don't know it. If they > were to find out, it might help provide funding and other resources > to spur development. Selective ACKnowledgment (SACK) allows acknowledgment of received packets in a TCP window so that only the missing/damaged packet needs to be re-transmitted. This is normally of little value on a LAN where ACKs arrive quickly and windows are smaller and no use on slow circuits. On fat pipes with latency and big windows it is a huge win as it allows you to recover much faster from a packet drop. If you don't have SACK, you need to re-transmit all of the packets in flight within the window while with SACK, you need only retransmit the dropped packet(s). If you have a 10 or 20 MB window, this is a big deal. Dynamic window sizing will make it of less significance in LANs as the windows will not be very large. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634