Date: Tue, 25 Jul 2006 15:50:47 +0100 From: "Peter Edwards" <peadar.edwards@gmail.com> To: "Jim Rees" <rees@umich.edu> Cc: fs@freebsd.org, rick@snowhite.cis.uoguelph.ca Subject: Re: freebsd4.11 patch for nfs over tcp Message-ID: <34cb7c840607250750u1590d371w6655cc60a8736be6@mail.gmail.com> In-Reply-To: <20060725135945.94DC81BBF0@citi.umich.edu> References: <34cb7c840607250309t1b20179icb034cad7e720e7f@mail.gmail.com> <20060725135945.94DC81BBF0@citi.umich.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/25/06, Jim Rees <rees@umich.edu> wrote: > I see by inspecting the code that you are right and the web site I consulted > was wrong. Don't believe everything you read on the web. > :-) I always point people at "Rethinking the TCP Nagle Algorithm" (Mogul & Minshall) when this comes up. It's a nice readable paper on the issues and some propsed solutions. http://www.acm.org/sigs/sigcomm/ccr/archive/2001/jan01/ccr-200101-mogul.pdf > I also see that Nagle himself suggests not using his algorithm with delayed > acks. It can work, but all the timers have to be just right. > > Anyway this bug was fixed a while ago, and I don't think there will be > another 4.x kernel, so there's not much to be done about this. > Absolutely. just setting things straight "for the record."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34cb7c840607250750u1590d371w6655cc60a8736be6>