All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: testing crazy stuff with iproute2
Date: Fri, 28 Dec 2007 11:18:27 +0100	[thread overview]
Message-ID: <20071228101827.GE1618@ff.dom.local> (raw)
In-Reply-To: <20071227233749.M11574@visp.net.lb>

On Fri, Dec 28, 2007 at 01:44:17AM +0200, Denys Fedoryshchenko wrote:
...
> For bandwidth sharing it is perfect, but i want just to make things, which i 
> did with TBF - some time bursty speed, and then slow down to lower speed if 
> customer is using too much. In theory it has to work like this, but in 
> practice i am hitting wall. I tried it about 1 year ago, it was same thing, 
> just with another conditions. Seems cburst/burst a bit different thing, just 
> to make load on CPU by HTB less , at high speeds.

IMHO it's quite possible you're trying to use HTB to things it is
not intended to do. cburst/burst have to limit burstiness and not
change rates depending on load. But, maybe they could do the other
things too whith some tricks, I don't know. I think CBQ or maybe
HFSC could be better for you. But, if TBF works for you, and you
don't need sharing (lending) I don't understand why to 'fight'
with HTB at all. You could maybe use it only to get class hierarchy
with some high, not limiting rates, or even try e.g. prio + TBF
combination.

Regards,
Jarek P.

  reply	other threads:[~2007-12-28 10:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-26  4:57 testing crazy stuff with iproute2 Denys Fedoryshchenko
2007-12-27 21:09 ` Jarek Poplawski
2007-12-27 21:25   ` Denys Fedoryshchenko
2007-12-27 22:54     ` Jarek Poplawski
2007-12-27 23:44       ` Denys Fedoryshchenko
2007-12-28 10:18         ` Jarek Poplawski [this message]
2007-12-28 13:20           ` Denys Fedoryshchenko

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=20071228101827.GE1618@ff.dom.local \
    --to=jarkao2@gmail.com \
    --cc=denys@visp.net.lb \
    --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 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.