From: Ben Greear <greearb@candelatech.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Optimizing performance for lots of virtual stations.
Date: Fri, 15 Mar 2013 10:50:17 -0700 [thread overview]
Message-ID: <51435F59.7050403@candelatech.com> (raw)
In-Reply-To: <514356F3.4030408@candelatech.com>
On 03/15/2013 10:14 AM, Ben Greear wrote:
> I probably should have done this first of course..but here is a 'perf top' on
> the station machine (50 TCP streams transmitting on each of 50 stations,
> and 78 associated-but-mostly-idle stations:
>
> Looks like sta_info_get would be a good place to start :)
>
>
> ---------------------------------------------------------------------------------------------------------------------------
> PerfTop: 1890 irqs/sec kernel:87.9% exact: 0.0% [1000Hz cycles], (all, 2 CPUs)
> ---------------------------------------------------------------------------------------------------------------------------
>
> samples pcnt function DSO
> _______ _____ _______________________________ ______________
>
> 2261.00 20.8% sta_info_get [mac80211]
Ahh, crap...I see the problem. The 'sta->addr' is the MAC of the VAP,
so if I have 100 stations all connected to the same AP, then the hashing
is worthless and just ends up being a linear search.
Probably not going to be fun to fix that!
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2013-03-15 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 17:22 Optimizing performance for lots of virtual stations Ben Greear
2013-03-14 23:12 ` Felix Fietkau
2013-03-14 23:18 ` Ben Greear
2013-03-15 1:44 ` Felix Fietkau
2013-03-15 3:26 ` Ben Greear
2013-03-15 17:14 ` Ben Greear
2013-03-15 17:50 ` 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=51435F59.7050403@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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 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.