Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Justin Schoeman <justin@expertron.co.za>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB does not respect the prio parameter
Date: Fri, 07 Sep 2007 08:43:59 +0000	[thread overview]
Message-ID: <46E10F4F.5030104@expertron.co.za> (raw)
In-Reply-To: <46D52904.4040809@businessecurity.com>

Is quantum not perhaps a bit high?  Try setting it lower, and see what 
happens?

-justin

On 2007-08-29 08:06, Martin Björnsson wrote:
> Hi all,
> 
> I'm experimenting with HTB and the prio parameter and it does not give me results I
> expect. I've created 4 HTB classes:
> 
> 1:10 TCP ACKs                       (prio 0)
> 1:20 TCP traffic on dst port 10001  (prio 1)
> 1:30 TCP traffic on dst port 10000  (prio 2)
> 1:40 Default                        (prio 3)
> 
> ceil and rate parameters are the same for all 4 classes (rate is 1000kbit and ceil is
> 55000kbit).
> 
> Then I start 2 TCP flows on src/dst ports 10000 and 10001. The packets seem to be
> correctly classified by the filter (I get hits on classes 10, 20 and 30).
> 
> The problem is that I get the same throughput on both TCP flows. Shouldn't I get about
> 1000kbit through class 30 and much more through class 20 since it has higher priority?
> 
> 
> Here's my setup script:
> 
> #!/bin/sh
> /bin/tc qdisc add dev eth0 root handle 1: htb default 40 
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2007-09-07  8:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29  8:06 [LARTC] HTB does not respect the prio parameter Martin Björnsson
2007-08-29  8:58 ` bartekR
2007-08-29 10:50 ` Martin Björnsson
2007-08-29 10:56 ` Nikolay Kichukov
2007-09-06 21:26 ` Andy Furniss
2007-09-07  8:43 ` Justin Schoeman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46E10F4F.5030104@expertron.co.za \
    --to=justin@expertron.co.za \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox