linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC 1/2] mac80211:  Add vif hash for multi-station RX performance.
Date: Thu, 11 Apr 2013 09:11:14 -0700	[thread overview]
Message-ID: <5166E0A2.4050506@candelatech.com> (raw)
In-Reply-To: <1365671968.8272.35.camel@jlt4.sipsolutions.net>

On 04/11/2013 02:19 AM, Johannes Berg wrote:
> On Tue, 2013-04-09 at 10:54 -0700, Ben Greear wrote:

> Another question: Have you thought about hashing the virtual interfaces
> instead of the stations, and then hashing the stations inside each
> virtual interface? That would make it a bit of a two-level thing:
>
> A1 (in the frame) -> virtual interface
>      A2 (frame) -> station
>
> But it would address the TX side efficiently without "some_sta" since
> you know the virtual interface there already, and could potentially have
> less impact on the code? On TX it'd actually even be more efficient if
> you have more than 1 station per interface (right now you don't though)

A two-level hash might be helpful, but it might complicate the rx logic
a bit because at least in many cases you have to walk all sta in all
sdata, so would be some sort of double-loop.  Not that bad though,
and performance wise it should be similar.  Doing per-sdata hash should
also fix bad vhash collisions (such as if stations change a high-order
part of their MAC and leave the lowest octet the same).

On tx, if we assume good hash spread, then it should also have good
performance, and there is no case I can think of where having multiple
sta per station VIF would be needed, so very unlikely to have bad hash
performance.

But a question on all of this:  Are you assuming the current sta_hash on
the wiphy stays the same, or would you want it moved into the sdata as well?

I'd be willing to try it if you think it might be worth
pushing the result upstream.  If it's not going upstream anyway, then
I'll probably just stick with my some-sta and vhash patches at least until
they start conflicting bad enough with upstream to be worth re-visiting.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2013-04-11 16:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03 16:48 [RFC 1/2] mac80211: Add vif hash for multi-station RX performance greearb
2013-04-03 16:48 ` [RFC 2/2] mac80211: Add vhash to debugfs greearb
2013-04-09  9:57 ` [RFC 1/2] mac80211: Add vif hash for multi-station RX performance Johannes Berg
2013-04-09 17:54   ` Ben Greear
2013-04-11  9:19     ` Johannes Berg
2013-04-11 16:11       ` Ben Greear [this message]
2013-04-23 19:42       ` Ben Greear
2013-04-23 22:06         ` Ben Greear
2013-04-24 11:01           ` Johannes Berg

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=5166E0A2.4050506@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).