All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Maxwell <greg@linuxpower.cx>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SFQ buckets/extensions
Date: Sat, 08 Jun 2002 18:42:33 +0000	[thread overview]
Message-ID: <marc-lartc-102356185029432@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102329319618482@msgid-missing>

On Fri, Jun 07, 2002 at 04:37:07PM +0200, Jan Coppens wrote:
> Why not implementing the sfb (stochastic fair Blue)? From the papers I read,
> the algorithm with the double buffered moving hash extension, seemed like a
> better alternative for the FRED, Stochastic fair RED and SFQ.

I'd like to toss in a request that anyone who impliments this please make
the bloom filter size adjustable and provide a mask to remove information
from the hash (i.e. sport/dport) to allow for per host fairness rather then
per flow.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2002-06-08 18:42 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
2002-06-07 19:08 ` Martin Devera
2002-06-07 19:50 ` Michael T. Babcock
2002-06-08 18:42 ` Gregory Maxwell [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-102356185029432@msgid-missing \
    --to=greg@linuxpower.cx \
    --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.