linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: Ben Greear <greearb@candelatech.com>, Eliad Peller <eliad@wizery.com>
Subject: Re: [PATCH] mac80211: optimise AP stop RCU handling
Date: Thu, 20 Dec 2012 12:16:42 +0100	[thread overview]
Message-ID: <1356002202.10029.3.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1355493476-2927-1-git-send-email-johannes@sipsolutions.net> (sfid-20121214_145817_787355_201B178C)

On Fri, 2012-12-14 at 14:57 +0100, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
> 
> If there are VLANs, stopping an AP is inefficient as it
> calls rcu_barrier() once for each interface (the VLANs
> and the AP itself). Optimise this by moving rcu_barrier()
> out of the station cleanups and calling it only once for
> all interfaces combined.

Applied.

johannes


  reply	other threads:[~2012-12-20 11:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13 22:59 [PATCH 0/5] mac80211: fix station cleanup/destruction Johannes Berg
2012-12-13 22:59 ` [PATCH 1/5] mac80211: fix station destruction in AP/mesh modes Johannes Berg
2012-12-13 22:59 ` [PATCH 2/5] mac80211: use del_timer_sync for final sta cleanup timer deletion Johannes Berg
2012-12-13 23:26   ` Johannes Berg
2012-12-13 22:59 ` [PATCH 3/5] mac80211: remove final sta_info_flush() Johannes Berg
2012-12-13 22:59 ` [PATCH 4/5] mac80211: warn if unexpectedly removing stations Johannes Berg
2012-12-13 22:59 ` [PATCH 5/5] mac80211: optimise roaming time again Johannes Berg
2012-12-13 23:32   ` Eliad Peller
2012-12-13 23:41     ` Johannes Berg
2012-12-13 23:57       ` Eliad Peller
2012-12-14  8:33         ` Johannes Berg
2012-12-14 13:57 ` [PATCH] mac80211: optimise AP stop RCU handling Johannes Berg
2012-12-20 11:16   ` Johannes Berg [this message]
2012-12-14 18:08 ` [PATCH 0/5] mac80211: fix station cleanup/destruction Ben Greear
2012-12-20 11:12 ` Johannes Berg

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=1356002202.10029.3.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=eliad@wizery.com \
    --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).