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:52:29 +0000 [thread overview]
Message-ID: <4706EA5D.2030900@boreham.org> (raw)
In-Reply-To: <47064579.3020001@boreham.org>
Peter V. Saveliev wrote:
> <skip />
>
> Simple packet drop works for ordinary tcp congestion algorithms as a channel
> overload, and tcp decreases speed. So works RED policing filters and so on.
>
Well...red isn't exactly 'simple' packet drop :)
In fact, if I could combine packet-rate-limit with red or sfq I'd be
very happy.
> Beside of this, iptables can _accept_ a packet :) You can try to mark and
> queue the excess packets.
>
Hmm...need more coffee...
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-10-06 1:52 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
2007-10-06 1:47 ` Peter V. Saveliev
2007-10-06 1:52 ` David Boreham [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=4706EA5D.2030900@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.