All of lore.kernel.org
 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: Fri, 15 Mar 2013 10:14:27 -0700	[thread overview]
Message-ID: <514356F3.4030408@candelatech.com> (raw)
In-Reply-To: <514294ED.7040909@candelatech.com>

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]
              1707.00 15.7% ieee80211_tx_status             [mac80211]
              1192.00 11.0% intel_idle                      [kernel]
               462.00  4.3% __ieee80211_recalc_idle         [mac80211]
               414.00  3.8% ieee80211_prepare_and_rx_handle [mac80211]
               240.00  2.2% dev_queue_xmit_nit              [kernel]
               199.00  1.8% ieee80211_rx                    [mac80211]
               154.00  1.4% ieee80211_find_sta_by_ifaddr    [mac80211]
               124.00  1.1% read_hpet                       [kernel]
               101.00  0.9% _raw_spin_lock_irqsave          [kernel]
                92.00  0.8% __netif_receive_skb             [kernel]
                80.00  0.7% tg_load_down                    [kernel]
                76.00  0.7% fget_light                      [kernel]
                75.00  0.7% ieee80211_propagate_queue_wake  [mac80211]
                75.00  0.7% memcpy                          [kernel]
                71.00  0.7% __ieee80211_stop_queue          [mac80211]
                70.00  0.6% ipt_do_table                    [kernel]
                66.00  0.6% csum_partial_copy_generic       [kernel]
                65.00  0.6% datagram_poll                   [kernel]
                63.00  0.6% _raw_spin_lock_bh               [kernel]
                61.00  0.6% ath_get_rate                    [ath9k]
                49.00  0.5% ieee80211_subif_start_xmit      [mac80211]
                48.00  0.4% tcp_poll                        [kernel]

Thanks,
Ben

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


  reply	other threads:[~2013-03-15 17:14 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 [this message]
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=514356F3.4030408@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.