All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: [LARTC] SFQ buckets
Date: Tue, 04 Jun 2002 17:23:11 +0000	[thread overview]
Message-ID: <marc-lartc-102321147014980@msgid-missing> (raw)

Just a thought, after talking to a friend who's doing his master's work
on RED and other queueing algorithms ...

... What if SFQ were to start with a minimal number of buckets, and
track how 'deep' each bucket was, then go to a larger number of bits
(2/4 at a time?) if the buckets hit a certain depth?  Theoretically,
this would mean that 'fairness' would be achieved more often in current
collision situations but that a smaller number of buckets would be
necessary to achieve fairness in currently low-collision situations.

I haven't looked at the SFQ code in a while, so I don't know how much
benefit this would be in terms of processing time, or even how expensive
it would be to change hash sizes on the fly, but at a certain level of
resolution (+/- 2-4 bits), the changes wouldn't be terribly frequent
anyway.

I've always been a bit of a fan of self-tuning algorithms anyway :)
-- 
Michael T. Babcock
CTO, FibreSpeed Ltd. 

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-06-04 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 17:23 Michael T. Babcock [this message]
2002-06-04 18:39 ` [LARTC] SFQ buckets Martin Devera
2002-06-04 19:20 ` PiotR
2002-06-04 19:40 ` Martin Devera
2002-06-04 19:47 ` 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-102321147014980@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.