From: Jean Tourrilhes <jt@hpl.hp.com>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: TC-HTB issue : low throughput
Date: Mon, 9 Nov 2009 12:04:49 -0800 [thread overview]
Message-ID: <20091109200448.GA13015@bougret.hpl.hp.com> (raw)
In-Reply-To: <4AF60349.8000502@gmail.com>
On Sun, Nov 08, 2009 at 12:31:21AM +0100, Jarek Poplawski wrote:
> Jean Tourrilhes wrote, On 11/07/2009 03:43 AM:
>
> > Behaviour :
> > ---------
> >
> > If I add classes 1:2 and 1:3 :
> > Each host independantly : ~170 Mb/s.
> > Both host together, for 10.10.10.38 : ~106 Mb/s ;
> > Both host together, for 10.10.10.33 : ~135 Mb/s
> >
> > So, not only performance did drop significantely, but
> > prioritisation did not happen as expected.
>
> If these eths are vlans (or other virtuals) something like this
> often happens if you forget to set dev's txqueuelen before
> adding classes (or a subqdisc with some 'limit').
Thanks a lot ! I've just added :
ifconfig eth6.34 txqueuelen 5
And now I get 450 Mb/s + 133 Mb/s. Not perfect, but much much
better, and probably good enough for now ;-)
> > I've noticed that /sbin/tc calculates a very low burst
> > value. This is due to the content of /proc/net/psched. I'm wondering
> > if the burst calculation is what causes the issue here.
> > However, I tried with "burst 50kb" and saw no difference...
>
> There is (probably still) unfixed overflow in tc.
>
> BTW, v2.6.31 should be more exact (but so much...) for above 100mbit
> scheduling, especially with this patch to iproute2:
> http://marc.info/?l=linux-netdev&m=124453482324409&w=2
>
> Jarek P.
Thanks. I'll look into upgrading.
Regards,
Jean
prev parent reply other threads:[~2009-11-09 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-07 2:43 TC-HTB issue : low throughput Jean Tourrilhes
2009-11-07 23:31 ` Jarek Poplawski
2009-11-07 23:35 ` Jarek Poplawski
2009-11-09 20:04 ` Jean Tourrilhes [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=20091109200448.GA13015@bougret.hpl.hp.com \
--to=jt@hpl.hp.com \
--cc=jarkao2@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).