From: Eliad Peller <eliad@wizery.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>
Subject: [PATCH 0/2] make roaming a bit faster
Date: Wed, 5 Sep 2012 20:23:55 +0300 [thread overview]
Message-ID: <1346865837-32265-1-git-send-email-eliad@wizery.com> (raw)
The use of synchronize_rcu during roaming adds
a significant delay. try minimizing it by replacing
these calls with other alternatives.
Eliad Peller (2):
mac80211: use synchronize_net() on key destroying
mac80211: use call_rcu() on sta deletion
net/mac80211/iface.c | 5 ++
net/mac80211/key.c | 2 +-
net/mac80211/sta_info.c | 117 ++++++++++++++++++++++++++---------------------
net/mac80211/sta_info.h | 2 +
4 files changed, 73 insertions(+), 53 deletions(-)
--
1.7.6.401.g6a319
next reply other threads:[~2012-09-05 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 17:23 Eliad Peller [this message]
2012-09-05 17:23 ` [PATCH 1/2] mac80211: use synchronize_net() on key destroying Eliad Peller
2012-09-06 15:38 ` Johannes Berg
2012-09-05 17:23 ` [PATCH 2/2] mac80211: use call_rcu() on sta deletion Eliad Peller
2012-09-06 15:41 ` Johannes Berg
2012-09-06 21:17 ` Eliad Peller
2012-09-07 7:34 ` 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=1346865837-32265-1-git-send-email-eliad@wizery.com \
--to=eliad@wizery.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).