From: Jarek Poplawski <jarkao2@gmail.com>
To: Bill Fink <billfink@mindspring.com>
Cc: Rick Jones <rick.jones2@hp.com>,
Steven Brudenell <steven.brudenell@gmail.com>,
netdev@vger.kernel.org
Subject: Re: tbf/htb qdisc limitations
Date: Fri, 15 Oct 2010 08:18:26 +0000 [thread overview]
Message-ID: <20101015081826.GA7205@ff.dom.local> (raw)
In-Reply-To: <20101015023749.f085006b.billfink@mindspring.com>
On Fri, Oct 15, 2010 at 02:37:49AM -0400, Bill Fink wrote:
> On Thu, 14 Oct 2010, Jarek Poplawski wrote:
>
> > On Thu, Oct 14, 2010 at 08:09:39AM +0000, Jarek Poplawski wrote:
> > > On Thu, Oct 14, 2010 at 03:13:54AM -0400, Bill Fink wrote:
> > > > TSO/GSO was disabled and was using 9000-byte jumbo frames
> > > > (and specified mtu 9000 to tc command).
> > > >
> > > > Here was one attempt I made using tbf:
> > > >
> > > > tc qdisc add dev eth2 root handle 1: prio
> > > > tc qdisc add dev eth2 parent 1:1 handle 10: tbf rate 8900mbit buffer 1112500 limit 10000 mtu 9000
> > > > tc filter add dev eth2 protocol ip parent 1: prio 1 u32 match ip dst 192.168.1.23 flowid 10:1
> > > >
> > > > I tried many variations of the above, all without success.
> > >
> > > The main problem are smaller packets. If you had (almost) only 9000b
> > > frames this probably could work. [...]
> >
> > On the other hand, e.g. the limit above seems too low wrt mtu & rate.
>
> Actually, I discovered my commands above work just fine on
> a 2.6.35 box:
>
> i7test7% nuttcp -T10 -i1 192.168.1.17
> 1045.3125 MB / 1.00 sec = 8768.3573 Mbps 0 retrans
> 1045.6875 MB / 1.00 sec = 8772.0292 Mbps 0 retrans
> 1049.5625 MB / 1.00 sec = 8804.2627 Mbps 0 retrans
> 1043.1875 MB / 1.00 sec = 8750.9960 Mbps 0 retrans
> 1048.6875 MB / 1.00 sec = 8796.3246 Mbps 0 retrans
> 1033.4375 MB / 1.00 sec = 8669.3188 Mbps 0 retrans
> 1040.7500 MB / 1.00 sec = 8730.7057 Mbps 0 retrans
> 1047.0000 MB / 1.00 sec = 8783.2063 Mbps 0 retrans
> 1040.0000 MB / 1.00 sec = 8724.0564 Mbps 0 retrans
> 1037.4375 MB / 1.00 sec = 8702.5434 Mbps 0 retrans
>
> 10431.5608 MB / 10.00 sec = 8749.7542 Mbps 25 %TX 35 %RX 0 retrans 0.11 msRTT
>
> The problems I encountered were on a field system running
> 2.6.30.10. I will investigate upgrading the field system
> to 2.6.35.
This change from 2.6.31 should matter here:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.35.y.git;a=commit;h=a4a710c4a7490587406462bf1d54504b7783d7d7
Jarek P.
prev parent reply other threads:[~2010-10-15 8:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 20:58 tbf/htb qdisc limitations Steven Brudenell
2010-10-10 11:23 ` Jarek Poplawski
2010-10-11 22:27 ` Steven Brudenell
2010-10-12 10:10 ` Jarek Poplawski
2010-10-12 19:31 ` Steven Brudenell
2010-10-12 21:59 ` Jarek Poplawski
2010-10-12 22:17 ` Rick Jones
2010-10-13 6:26 ` Jarek Poplawski
2010-10-14 3:36 ` Bill Fink
2010-10-14 4:01 ` Eric Dumazet
2010-10-14 6:34 ` Bill Fink
2010-10-14 6:44 ` Jarek Poplawski
2010-10-14 7:13 ` Bill Fink
2010-10-14 8:09 ` Jarek Poplawski
2010-10-14 8:50 ` Jarek Poplawski
2010-10-15 6:37 ` Bill Fink
2010-10-15 6:44 ` Eric Dumazet
2010-10-15 21:37 ` Bill Fink
2010-10-15 22:05 ` Jarek Poplawski
2010-10-16 4:51 ` Bill Fink
2010-10-16 20:58 ` Jarek Poplawski
2010-10-17 1:24 ` Bill Fink
2010-10-17 20:36 ` Jarek Poplawski
2010-10-19 7:37 ` Bill Fink
2010-10-20 11:06 ` Jarek Poplawski
2010-10-27 4:51 ` Bill Fink
2010-10-27 9:48 ` Jarek Poplawski
2010-10-15 8:18 ` Jarek Poplawski [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=20101015081826.GA7205@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=billfink@mindspring.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=steven.brudenell@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).