Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Fatih Düzova" <fduzova@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] bandwidth control on htb
Date: Sat, 28 May 2005 15:37:53 +0000	[thread overview]
Message-ID: <103339c8050528083767284c8b@mail.gmail.com> (raw)

Hi,
I implemented queues on some ports with htb by filtering. and to have
a constant bw, i defined rate and ceil the same. But while watching
the bw's, I ve realized they may sometimes exceed the defined value
for short periods. How could I avoid this situation? I thought that
implementing a leaky bucket'd be fine but i m not sure about this and
how to do it on tc.
I would be glad if anyone could help me. Thanks,

Fatih DUZOVA
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2005-05-28 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-28 15:37 Fatih Düzova [this message]
2005-05-30 15:08 ` [LARTC] bandwidth control on htb Andy Furniss
2005-06-10  0:07 ` Andy Furniss

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=103339c8050528083767284c8b@mail.gmail.com \
    --to=fduzova@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox