From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Question on ieee80211_tx_status
Date: Wed, 24 Apr 2013 13:12:49 +0200 [thread overview]
Message-ID: <1366801969.21854.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <5176DD33.9000100@candelatech.com> (sfid-20130423_233115_840840_D02CAECE)
On Tue, 2013-04-23 at 12:12 -0700, Ben Greear wrote:
> It appears that ieee80211_tx_status also scales poorly
> when using large numbers of virtual stations connected
> to a single AP, due to for_each_sta_info(local, hdr->addr1, sta, tmp)...
>
> I'm going to try using the vif-hashing to make this faster,
> but first a question:
>
> Since it matches on MAC addresses, should it
> just return at the bottom of the loop since it has
> found a match, and MACs are supposed to be unique?
>
> for_each_sta_info(local, hdr->addr1, sta, tmp) {
> /* skip wrong virtual interface */
> if (!ether_addr_equal(hdr->addr2, sta->sdata->vif.addr))
> continue;
> ...
I think that'd be mostly safe, since we don't allow the same station to
be added to multiple VLANs. However, I'm not entirely sure if it really
is safe in the case of WDS interfaces.
> If so, that would be a good improvement since the hash can easily
> be turned into a linear search even in AP mode (without all of
> my virtual-station scenarios)...
I don't really see how the hash could be linear? When the low byte of
MAC addresses is the same, but otherwise?
johannes
next prev parent reply other threads:[~2013-04-24 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 19:12 Question on ieee80211_tx_status Ben Greear
2013-04-24 11:12 ` Johannes Berg [this message]
2013-04-24 16:00 ` Ben Greear
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=1366801969.21854.1.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--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).