From: Sean Conner <sean@conman.org>
To: bloat-devel@lists.bufferbloat.net
Subject: Re: A tiny almost sorta kinda nearly minimal perfect hash for a mac classifier?
Date: Sun, 13 Nov 2011 21:22:10 -0500 [thread overview]
Message-ID: <20111114022209.GA5769@brevard.conman.org> (raw)
In-Reply-To: <CAA93jw4R7YZXJAvWTeDg=VH47xzbrFudOhpKAd_4dPMHWvWTYw@mail.gmail.com>
It was thus said that the Great Dave Taht once stated:
> There's this class of non-algorithms where stupid and brute force
> nearly works. Then there are the be-all end-all algorithms which scale
> beautifully O(1) over n - so long as n is large enough to wipe out the
> overhead of the be-all-end-all algorithm, and taking locks, allocating
> memory at bad times, etc, is ok.
>
> I keep running into problems where brute force and a simple table
> lookup is almost enough.
>
> Here's one. I'd like to classify network streams so that they end up
> in a unique queue[x], based on their nexthop mac address in the ip
> header.
I've checked my home network, and the network of a small webhosting
company I do work for, and in both cases, the MAC addresses were all unique
in the lower 10-12 bits, which is understandable given that's the portion of
the MAC address vendors control.
Why not just use the lower N bits as the hash function?
-spc (Or am I missing something?)
next prev parent reply other threads:[~2011-11-14 2:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 20:43 Dave Taht
2011-11-14 2:22 ` Sean Conner [this message]
2011-11-14 2:41 ` Fred Baker
2011-11-14 7:44 ` Dave Taht
2011-11-14 8:13 ` Sean Conner
2011-11-14 8:21 ` Dave Taht
2011-11-15 21:14 ` Sean Conner
2011-11-15 21:44 ` Jonathan Morton
2011-11-15 22:19 ` Dave Taht
2011-11-15 22:20 ` Dave Taht
2011-11-14 8:20 Sean Conner
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=20111114022209.GA5769@brevard.conman.org \
--to=sean@conman.org \
--cc=bloat-devel@lists.bufferbloat.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox