From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] SFQ buckets/extensions
Date: Fri, 07 Jun 2002 19:01:12 +0000 [thread overview]
Message-ID: <marc-lartc-102347655914795@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102329319618482@msgid-missing>
> exactly. The discussion should be about how to implement if
> efficiently. What about to have N IP buckets and N IP/PORT
> buckets. When IP/PORT hash resolves to bucket then we could
> (re)link the
Consider a new classful queueing discipline "SFC" that behaves exactly
as SFQ does and can have only one sub-queue attached to it.
... SFC (8 bit hash against dest ip)
|
\-- SFC (11 bit hash against src ip, port, dest ip, port)
|
\-- dequeue ...
Is this even possible with how the classes are currently built in the
kernel?
--
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-06-07 19:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 16:04 [LARTC] SFQ buckets/extensions Don Cohen
2002-06-06 0:53 ` Alexander Atanasov
2002-06-06 6:01 ` Don Cohen
2002-06-06 13:05 ` Michael T. Babcock
2002-06-06 23:06 ` Alexander Atanasov
2002-06-06 23:38 ` Don Cohen
2002-06-07 1:33 ` Alexander Atanasov
2002-06-07 1:59 ` Don Cohen
2002-06-07 8:26 ` Alexander Atanasov
2002-06-07 14:18 ` Michael T. Babcock
2002-06-07 14:37 ` Jan Coppens
2002-06-07 16:14 ` Don Cohen
2002-06-07 18:13 ` Martin Devera
2002-06-07 18:38 ` Martin Devera
2002-06-07 19:01 ` Michael T. Babcock [this message]
2002-06-07 19:08 ` Martin Devera
2002-06-07 19:50 ` Michael T. Babcock
2002-06-08 18:42 ` Gregory Maxwell
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-102347655914795@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.