linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 14 Mar 2013 16:18:09 -0700	[thread overview]
Message-ID: <51425AB1.9090603@candelatech.com> (raw)
In-Reply-To: <51425963.2000904@openwrt.org>

On 03/14/2013 04:12 PM, Felix Fietkau wrote:
> On 2013-03-14 6:22 PM, Ben Greear wrote:
>> I've been doing some performance testing, and having lots of
>> stations causes quite a drag:  total throughput with 1 station: 250Mbps TCP throughput,
>> total with 50 stations:  225 Mbps, and with 128 stations: 20-40Mbps (it varies a lot..not so sure why).
>>
>> I poked around in the rx logic and it seems the rx-data path is fairly
>> clean for data packets.  But, from what I can tell, each beacon is going
>> to cause an skb_copy() call and a queued work-item for each station interface,
>> and there are going to be lots of beacons per second in most scenarios...
>>
>> I was wondering if this could be optimized a bit to special case beacons
>> and not make a new copy (or possibly move some of the beacon handling
>> logic up to the radio object and out of the sdata).
>>
>> And of course, it could be there are more important optimizations...I'm curious
>> if anyone is aware of any other code that should be optimized to have better
>> performance with lots of stations...
> How about doing some profiling with lots of stations - that should
> hopefully reveal where the real bottleneck is.
> By the way, with that many stations and low throughput, is the CPU usage
> on your system significantly higher, or could it just be some extra
> latency introduced somewhere else in the code?

CPU load is fairly high, but doesn't seem to just be CPU bound.  Maybe
lots and lots of work items all piled up or something like that...

I'll work on some profiling as soon as I get a chance.

I'm suspicious that the the management frame handling will
need some optimization though..I think it basically copies
the skb and broadcasts all mgt frames to all running stations....

Thanks,
Ben

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


  reply	other threads:[~2013-03-14 23:18 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 [this message]
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

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=51425AB1.9090603@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 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).