All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Boreham <david_list@boreham.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] shaping by packet count rather than bytes ?
Date: Sat, 06 Oct 2007 01:16:38 +0000	[thread overview]
Message-ID: <4706E1F6.2070006@boreham.org> (raw)
In-Reply-To: <47064579.3020001@boreham.org>

David Boreham wrote:
>> iptables: limit, hashlimit, dstlimit work on pps basis.
>>   
> <doh> ! yes, I'd thought about that stuff but somehow
> discounted it as 'not worthy' for traffic shaping.
Actually, I remember now why iptables doesn't work :

All it does is drop the excess packets over the limit.

That's not what I need. Rather , I want something like a
tbf that operates on packet count rather than byte count.
Thus, packets will be send at the configured rate, and
queued up if they arrive at a rate in excess of the limit.

iptables will simply drop the excess, which I'm sure will
lead to poor throughput and of course means that there's no
queue to manage to achieve a given QoS policy.

Rewriting tbf or htb to operate on packets not
bytes _seems_ like it'd do the trick.

I'm a bit surprised that nobody has made this their masters thesis ;)


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

  parent reply	other threads:[~2007-10-06  1:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 14:08 [LARTC] shaping by packet count rather than bytes ? David Boreham
2007-10-05 18:56 ` Jens Thiele
2007-10-05 23:43 ` Peter V. Saveliev
2007-10-06  1:04 ` David Boreham
2007-10-06  1:16 ` David Boreham [this message]
2007-10-06  1:47 ` Peter V. Saveliev
2007-10-06  1:52 ` David Boreham

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=4706E1F6.2070006@boreham.org \
    --to=david_list@boreham.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.