From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: [LARTC] SFQ + RED
Date: Tue, 27 Nov 2001 16:53:10 +0000 [thread overview]
Message-ID: <marc-lartc-100694050303443@msgid-missing> (raw)
I've asked this before, but does anyone feel technically inclined
enough to try swapping in a RED queue for the per-bucket queuing done
by SFQ? If SFQ builds a series of 'sessions' to be given fair use of
available bandwidth, using RED to slow down those that are building up
too fast would smooth things out.
Just a thought ...
--
Michael T. Babcock
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-11-27 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 16:53 Michael T. Babcock [this message]
2001-12-03 14:10 ` [LARTC] SFQ + RED 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
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-100694050303443@msgid-missing \
--to=mbabcock@fibrespeed.net \
--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