From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Anything out there that is similar to Cisco's WFQ?
Date: Wed, 10 Jul 2002 20:31:02 +0000 [thread overview]
Message-ID: <marc-lartc-102633315600819@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102631718111475@msgid-missing>
Don Cohen wrote:
> > From: "CIT/Paul" <xerox@foonet.net>
> > Any help would be greatly appreciated :) This is much better than SFQ :>
>
>Sounds like SFQ to me. Can you tell us what the differences are?
>
>
PRIO'd SFQ.
If you had classful PRIO with SFQ on each band, you'd probably have a
similar effect to what's been described; just a guess though. It seems
the desire is to 'ignore' low-priority bands if high-priority bands have
traffic, and to balance between those sessions.
--
Michael T. Babcock
CTO, FibreSpeed Ltd.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-07-10 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 15:57 [LARTC] Anything out there that is similar to Cisco's WFQ? CIT/Paul
2002-07-10 19:55 ` Don Cohen
2002-07-10 20:31 ` Michael T. Babcock [this message]
2002-07-11 2:15 ` S Mohan
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-102633315600819@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 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.