All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Best way to limit the rate
Date: Fri, 29 Nov 2002 18:36:07 +0000	[thread overview]
Message-ID: <marc-lartc-103859510006534@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103857550920952@msgid-missing>

On Friday 29 November 2002 14:10, Mathieu Deziel wrote:
> Suppose you need to limit the rate of the traffic that flows in an HTB
> leaf class to 32kbits/sec
>
> I can think of three ways to do it:
>
> 1.
> make rate = ceil = 32kbit when creating this HTB leaf class.  A pfifo
> qdisc can then be attached to this HTB leaf class to reduce the queue
> size, and therefore reduce the latency of the packets.
>
> 2.
> Attach a TBF qdisc to this HTB leaf class, and configure it properly.
HTB _is_ TBF.  So the first idea is better.  A ceiled htb class = tbf qdisc.

> 3.
> Have a policing filter before the HTB leaf class that will limit the
> rate of the traffic before it enters the HTB leaf class.
>
> Which one of these methods is the best?
> My tests have shown that the latency of the packets is dramatically
> better with method 3.  Anybody has an idea why this is the case?
Solution 3 has the advantage that you limit the packet at a rate, but you 
don't have a queue.  The policer uses a small tbf queue to limit the packets.  
The packets are simply dropped if they exceed a certain rate.  It's also not 
possible to share bandwidth like you can do with cbq/htb.

Stef


-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2002-11-29 18:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-29 13:10 [LARTC] Best way to limit the rate Mathieu Deziel
2002-11-29 18:36 ` Stef Coene [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=marc-lartc-103859510006534@msgid-missing \
    --to=stef.coene@docum.org \
    --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.