Date: Sat, 20 Mar 2004 14:19:22 -0800 From: Luigi Rizzo <rizzo@icir.org> To: Vincent Poy <vince@oahu.wurldlink.net> Cc: questions@freebsd.org Subject: Re: Latency problem with traffic shaping (ipfw/dummynet) Message-ID: <20040320141922.B7314@xorpc.icir.org> In-Reply-To: <20040320011336.C8264-100000@oahu.WURLDLINK.NET>; from vince@oahu.wurldlink.net on Sat, Mar 20, 2004 at 01:14:38AM -1000 References: <20040320011336.C8264-100000@oahu.WURLDLINK.NET>
next in thread | previous in thread | raw e-mail | index | archive | help
cannot comment on the reason for the huge delay (but one
way to check what is going on is to change the pipe's bandwidth
and see if anything changes), but i see a big
misunderstanding on weights vs. priorities in your
configuration:
> # Define our upload pipe
> ${fwcmd} pipe 1 config bw 480Kbit/s
> # Define a high-priority queue
> ${fwcmd} queue 1 config pipe 1 weight 100
> # Define a medium-high-priority queue
> ${fwcmd} queue 2 config pipe 1 weight 99
> # Define a medium-low-priority queue
> ${fwcmd} queue 3 config pipe 1 weight 98
> # Define a low-priority queue
> ${fwcmd} queue 4 config pipe 1 weight 97
the above configuration means that if queue 1 is getting a bandwidth
X, then queue 2 will get 0.99X, queue 3 will get 0.98X, queue
4 will get 0.97X. Hardly matching any reasonable definition of high-mid-low
priority!
cheers
luigi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040320141922.B7314>