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" <linux-wireless@vger.kernel.org>
Subject: Re: Question on ieee80211_tx_status
Date: Wed, 24 Apr 2013 09:00:24 -0700	[thread overview]
Message-ID: <51780198.4060602@candelatech.com> (raw)
In-Reply-To: <1366801969.21854.1.camel@jlt4.sipsolutions.net>

On 04/24/2013 04:12 AM, Johannes Berg wrote:
> 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.

Would you ever need to send an ACK multiple times?  If so, then
my approach would be wrong, but if you never should, then my
approach would be more right than the current code.

It would seem to me that you should never ack a packet more
than once, but I don't actually know enough about the protocol
to know if that is a valid assumption.

>> 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?

Sure, just randomize octed 3 and 4 and leave octet 5 the
same.  Easily done in certain test tools :)

The new RFC patch I posted uses a better hash, and fixes all
of the linear walk issues that show up in 'perf top' with
300 stations on a relatively weak Atom system...

Also, to deal with cases where sdata may have duplicate macs,
I just added a for_each_sdata() macro that should quickly
walk a hash list of sdata objects and get the same behaviour
efficiently (assuming that you don't have large amounts of
sdata with the same MAC, but that seems unlikely to happen).

Thanks,
Ben


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


      reply	other threads:[~2013-04-24 16:00 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
2013-04-24 16:00   ` Ben Greear [this message]

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=51780198.4060602@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).