From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] SFQ buckets
Date: Tue, 04 Jun 2002 19:47:25 +0000 [thread overview]
Message-ID: <marc-lartc-102322010724892@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102321147014980@msgid-missing>
> This is often discussed and is on "TODO" for someone
>
> > SFQ is connection oriented. right?
> > Would be a good idea to make the queues per ip rather than per tcp
> > flow? So there would be per host fairnes.
And all the discussions tend to lead to the conclusion that there should
be an sfq option (when the queue is created) for:
a) how big the hash is
b) whether to take into account source ports or not
c) whether to take into account destination ports or not
d) etc. :)
Maybe someone who's written a qdisc would feel up to this?
--
Michael T. Babcock
CTO, FibreSpeed Ltd.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-06-04 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 17:23 [LARTC] SFQ buckets Michael T. Babcock
2002-06-04 18:39 ` Martin Devera
2002-06-04 19:20 ` PiotR
2002-06-04 19:40 ` Martin Devera
2002-06-04 19:47 ` Michael T. Babcock [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-102322010724892@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.