From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SFQ working
Date: Tue, 11 Dec 2001 21:12:54 +0000 [thread overview]
Message-ID: <marc-lartc-100810520327171@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100810280920305@msgid-missing>
On Tue, Dec 11, 2001 at 02:32:44PM -0600, Amit Kucheria wrote:
> Just an "understanding check"(tm) ;)
>
> From what i gathered from the SFQ documents, SFQ *has* to be contained in
> classes and it will give 'different' flows in _that_ class a chance by
> reordering packets.
That's partly true. Yes, it gives flows in _that_ class a chance by
scheduling packets. However, if you are talking to a real modem or a really
congested link (so the cable is full, so to speak), then you don't need a
class to nest it in.
> Here different flows are distinguished by source & dest addresses and
> source port.
>
> Is this right?
Exactly.
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/lartc/
prev parent reply other threads:[~2001-12-11 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 20:32 [LARTC] SFQ working Amit Kucheria
2001-12-11 21:12 ` bert hubert [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=marc-lartc-100810520327171@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 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.