From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SFQ + RED
Date: Thu, 06 Dec 2001 16:23:50 +0000 [thread overview]
Message-ID: <marc-lartc-100765586801167@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100694050303443@msgid-missing>
On Tue, Dec 04, 2001 at 01:27:02PM -0500, Michael T. Babcock wrote:
> > The random variation in demand from other flows will have the effect
> > of jittering the maximum length of your subqueue, which is pretty
> > similar to what you experience with RED, isn't it?
>
> Not quite, no. The dropping of packets is based on actual calculations in
> RED that aren't available in SFQ. SFQ drops _all_ the packets off the end
> and doesn't start doing so before congestion happens -- RED is designed to
> drop packets before getting overly congested so that the stream speeds stay
> steady and don't try to climb above what's available.
GRED might be what you want, if you can get anybody to explain you how it
works. I don't get it yet.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
Trilab The Technology People
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-12-06 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 16:53 [LARTC] SFQ + RED Michael T. Babcock
2001-12-03 14:10 ` bert hubert
2001-12-03 21:05 ` Michael T. Babcock
2001-12-03 23:32 ` Don Cohen
2001-12-04 7:58 ` Martin Devera
2001-12-04 18:27 ` Michael T. Babcock
2001-12-06 16:23 ` bert hubert [this message]
2001-12-06 16:37 ` Michael T. Babcock
2001-12-06 18:12 ` bert hubert
2002-06-06 9:21 ` Jan Coppens
2002-06-06 11:38 ` Alexey Talikov
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-100765586801167@msgid-missing \
--to=ahu@ds9a.nl \
--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