From: Andrew Beverley <andy@andybev.com>
To: lartc@vger.kernel.org
Subject: Re: Egress bandwidth limiting not working?
Date: Wed, 08 May 2013 06:10:17 +0000 [thread overview]
Message-ID: <1367993417.3543.180.camel@andrew-desktop> (raw)
In-Reply-To: <5188DD0D.4020708@open-t.co.uk>
On Tue, 2013-05-07 at 11:53 +0100, Sebastian Arcus wrote:
> I am trying to limit the bandwidth used by the egress leg as per the
> lartc cookbook here:
> http://www.lartc.org/howto/lartc.cookbook.ultimate-tc.html
>
> The ingress works fine (well, it is a bit wobbly - but it limits the
> rate at roughly the expected level). However, the egress doesn't appear
> to be working. With no tc active, I get about 300mbs both ways (I'm
> testing in VMs). When it is on, the ingress is down to roughly 500kbs,
> but the egress is down to only about *150mbs*.
Have you tried a qdisc other than CBQ, such as HTB? I've never actually
used CBQ myself, but from the LARTC HOWTO:
"CBQ is the most complex qdisc available, the most hyped, the least
understood, and probably the trickiest one to get right. This is not
because the authors are evil or incompetent, far from it, it's just that
the CBQ algorithm isn't all that precise and doesn't really match the
way Linux works."
Are you just trying to achieve simple policing of the interface, or
something more advanced?
Andy
next prev parent reply other threads:[~2013-05-08 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 10:53 Egress bandwidth limiting not working? Sebastian Arcus
2013-05-08 6:10 ` Andrew Beverley [this message]
2013-05-08 7:03 ` Sebastian Arcus
2013-05-08 17:24 ` Andrew Beverley
2013-05-08 18:29 ` Sebastian Arcus
2013-05-14 19:38 ` Andrew Beverley
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=1367993417.3543.180.camel@andrew-desktop \
--to=andy@andybev.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.