Date: Fri, 11 Mar 2005 01:24:33 -0800 From: Luigi Rizzo <rizzo@icir.org> To: jim song <jingmin.song@gmail.com> Cc: freebsd-ipfw@freebsd.org Subject: Re: why my dummynet queue not work? Message-ID: <20050311012433.C66627@xorpc.icir.org> In-Reply-To: <d018391a050310220622b50cd3@mail.gmail.com>; from jingmin.song@gmail.com on Fri, Mar 11, 2005 at 02:06:02PM %2B0800 References: <d018391a050310200327a01c48@mail.gmail.com> <20050311043933.GA28686@odin.ac.hmc.edu> <d018391a050310213469df3025@mail.gmail.com> <20050310215250.A65126@xorpc.icir.org> <d018391a050310220622b50cd3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 11, 2005 at 02:06:02PM +0800, jim song wrote: > Luigi, > > I think what you said is the working window. It could be different to > the initial window I set for the tcp stream. Tcp should get full bandwidth > throughput in such circumstance. > > But in my testing, tcp window has retreated from 5M window to 640K. > That is the problem. > > Am I right? i think you are just being lazy :) seriously, i don't mean to be rude but brooks and i and possibly others already suggested that it is likely a window problem (as we have already been hit by that). What you should do is do your homework and run a few experiments with different delay settings, taking note of the actual delays (with a PING measurement e.g) and bandwidths, and figure out if there is a window/rtt pattern and in case determine what window is in use. then there are (as we already said) multiple parameters that cap the window: the TCP window, the socket buffer, window scale options etc on both sender and receiver. cheers luigi > Thanks, > --Jim > _______________________________________________ > freebsd-ipfw@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw > To unsubscribe, send any mail to "freebsd-ipfw-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050311012433.C66627>