mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mattias Rönnblom" <hofors@lysator.liu.se>
To: linux-kernel@vger.kernel.org
Subject: Leaky Bucket qdisc
Date: Sat, 09 Jan 2010 19:12:10 +0100	[thread overview]
Message-ID: <87d41jrvut.fsf@isengard.friendlyfire.se> (raw)

Hi all,

to learn a little something about the kernel and to be able to do some
benchmarks on the HR timers I wrote a leaky bucket traffic shaping
qdisc.

For those who don't know, leaky bucket requires (very) high resolution
timers, and is more strict than TBF in that it doesn't allow a burst
(other than a single frame will go out at a line speed, of course).

However, my understanding from the TBF qdisc documentation is that you
can achieve the same effect with TBF, even to the point of not
allowing any bursts, which makes LB pretty much redundant. I thought I
would send this e-mail anyway, to see if there was some interest in
this little piece of code. If so, I'll try to clean it up and submit
it.

One benefit with LB is that it's very easy to configure. There's only
one parameter: the configured rate. It's non-work conserving and my
implementation is classless, with an inner qdisc, just like TBF. I've
patched 'tc' too to cope with LB.

It requires HR timers, and the better timers, the closer to the
configured rate you'll get. My system's timer resolution allows me to
shape with up to about 100 Mbit/s, if I recall correctly.

Best regards,
     Mattias

             reply	other threads:[~2010-01-09 18:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-09 18:12 Mattias Rönnblom [this message]
2010-01-10  7:04 ` David Miller

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=87d41jrvut.fsf@isengard.friendlyfire.se \
    --to=hofors@lysator.liu.se \
    --cc=linux-kernel@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

Powered by JetHome