From: Johannes Berg <johannes@sipsolutions.net>
To: Eliad Peller <eliad@wizery.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] mac80211: use synchronize_net() on key destroying
Date: Thu, 06 Sep 2012 17:38:12 +0200 [thread overview]
Message-ID: <1346945892.5469.19.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1346865837-32265-2-git-send-email-eliad@wizery.com> (sfid-20120905_192353_681041_CEDFC81E)
On Wed, 2012-09-05 at 20:23 +0300, Eliad Peller wrote:
> __ieee80211_key_destroy() calls synchronize_rcu() in
> order to sync the tx path before destroying the key.
>
> However, synching the tx path can be done with
> synchronize_net() as well, which is usually faster
> (the timing might be important for roaming scenarios).
Applied.
johannes
next prev parent reply other threads:[~2012-09-06 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 17:23 [PATCH 0/2] make roaming a bit faster Eliad Peller
2012-09-05 17:23 ` [PATCH 1/2] mac80211: use synchronize_net() on key destroying Eliad Peller
2012-09-06 15:38 ` Johannes Berg [this message]
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=1346945892.5469.19.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=eliad@wizery.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).