All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb overrate with 2.6.16
Date: Sat, 15 Apr 2006 23:13:33 +0000	[thread overview]
Message-ID: <44417E1D.50301@dsl.pipex.com> (raw)
In-Reply-To: <1145095091.18168.26.camel@indigo.declera.com>

Yanko Kaneti wrote:
> Hi
> 
> Here is something that worked with with 2.6.10-1.771_FC2smp and stopped
> working when I upgraded to 2.6.16-1.2069_FC4smp.
> These are fedora kernels and the network controller is an Intel Gbit
> (e1000) running a 100 Mbps Full Duplex.
> Don't know how or if this matters but the 2.6.10 kernel has
> CONFIG_X86_HZ\x1000 and the 2.6.16 has CONFIG_HZ%0
> 
> The idea is to just shape to , say 2Mbit, a certain kind of traffic
> everything else should goes unshaped.
> 
> # tc qdisc add dev eth0 root handle 1: htb default 20

Why default 20 - if you don't have 1:20 it would be better to use 
default 0 which is unshaped and is the default - so ommitting default is 
the same - unclassifed traffic goes through unshaped.

> # tc class add dev eth0 parent 1: classid 1:2 htb rate 2Mbit
> # tc qdisc add dev eth0 parent 1:2 sfq perturb 10
> # tc filter add dev eth0 protocol ip parent 1:0 prio 1 handle 50 fw flowid 1:2
> 
> This was working as expected with 2.6.10
> I've tried creating a proper 1:1 100Mbit parent to be the default but it
> didn't help. And it was working fine without it on 2.6.10
> 
> With the 2.6.16 kernel I get results like
> 
> # tc -s -d class show dev eth0
> class htb 1:2 root leaf 800b: prio 0 quantum 25000 rate 2000Kbit ceil 2000Kbit burst 2600b/8 mpu 0b overhead 0b cburst 2600b/8 mpu 0b overhead 0b level 0
>  Sent 189796883 bytes 20626 pkt (dropped 0, overlimits 0 requeues 0)
>  rate 3484Kbit 45pps backlog 0b 0p requeues 0
>  lended: 20627 borrowed: 0 giants: 30926

The giants are the problem - if you specify mtu XXXXX on 1:2 class it 
should work.

Or you could consider setting mtu on nic to 1500 if that is practical 
for you ie. this traffic is headed somewhere that is going to frag it 
down to 1500 anyway.

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2006-04-15 23:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-15  9:58 [LARTC] htb overrate with 2.6.16 Yanko Kaneti
2006-04-15 23:13 ` Andy Furniss [this message]
2006-04-16  0:19 ` Yanko Kaneti
2006-04-16  2:03 ` Andy Furniss
2006-04-16  2:37 ` Yanko Kaneti
2006-04-16 18:40 ` Andy Furniss
2006-04-16 20:03 ` Yanko Kaneti
2006-04-16 21:10 ` Andy Furniss
2006-04-17 19:03 ` Andy Furniss
2006-04-17 19:32 ` Patrick McHardy
2006-04-17 21:02 ` Yanko Kaneti
2006-04-18 11:25 ` Andy Furniss
2006-04-18 11:36 ` Andy Furniss
2006-04-18 13:05 ` Andy Furniss

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=44417E1D.50301@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.