From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] (E)SFQ suggestion
Date: Thu, 06 Jun 2002 12:40:43 +0000 [thread overview]
Message-ID: <marc-lartc-102336728913014@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102335607205273@msgid-missing>
> There are attempts to replace hashing routine in SFQ to
> consider IPs or ports.
> What about to use HRR - roundrobin around bunch of IP
> adresses and then smaller WRR for ports per IP ?
> It would solve both problems - fairnes between computers
> (IP) and between flows on than single computer ...
Basically you're suggesting a multi-staged hash bucket ... hash each packet
twice; once against the source IPs, then against the same criteria as now.
Do a loop through the first hash list, pick a bucket, then use the second
hash to pick packets from that bucket. Any thoughts?
--
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-06 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 9:33 [LARTC] (E)SFQ suggestion Martin Devera
2002-06-06 12:40 ` Michael T. Babcock [this message]
2002-06-06 23:47 ` Alexander Atanasov
2002-06-07 14:20 ` Michael T. Babcock
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-102336728913014@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.