From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Thomas Graf <tgraf@suug.ch>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [RFC] mac80211: use rhashtable for station table
Date: Fri, 13 Feb 2015 14:13:06 -0800 [thread overview]
Message-ID: <54DE76F2.4080107@candelatech.com> (raw)
In-Reply-To: <1423864049-8961-1-git-send-email-johannes@sipsolutions.net>
On 02/13/2015 01:47 PM, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> We currently have a hand-rolled table with 256 entries and are
> using the last byte of the MAC address as the hash. This hash
> is obviously very fast, but collisions are easily created and
> we waste a lot of space in the common case of just connecting
> as a client to an AP where we just have a single station. The
> other common case of an AP is also suboptimal due to the size
> of the hash table and the ease of causing collisions.
>
> Convert all of this to use rhashtable with jhash, which gives
> us the advantage of a far better hash function (with random
> perturbation to avoid hash collision attacks) and of course
> that the hash table grows and shrinks dynamically with chain
> length, improving both cases above.
Oooh, maybe finally time to mix local addr with peer addr to
make lots of vifs connected to same AP hash well too? :)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2015-02-13 22:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 21:47 [RFC] mac80211: use rhashtable for station table Johannes Berg
2015-02-13 22:13 ` Ben Greear [this message]
2015-02-23 16:32 ` Johannes Berg
2015-02-14 2:14 ` Sergey Ryazanov
2015-02-23 16:33 ` Johannes Berg
2015-02-23 21:26 ` Sergey Ryazanov
2015-02-23 21:52 ` Johannes Berg
2015-02-23 22:01 ` Johannes Berg
2015-02-23 22:07 ` Johannes Berg
2015-02-23 22:15 ` Sergey Ryazanov
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=54DE76F2.4080107@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tgraf@suug.ch \
/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.