From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: yogeshp@marvell.com
Subject: Re: [PATCH] mac80211: defer tailroom counter manipulation when roaming
Date: Mon, 04 Mar 2013 16:34:36 +0100 [thread overview]
Message-ID: <1362411276.21028.24.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1362089950-12142-1-git-send-email-johannes@sipsolutions.net> (sfid-20130228_231919_069651_BE886B2B)
On Thu, 2013-02-28 at 23:19 +0100, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> During roaming, the crypto_tx_tailroom_needed_cnt counter
> will often take values 2,1,0,1,2 because first keys are
> removed and then new keys are added. This is inefficient
> because during the 0->1 transition, synchronize_net must
> be called to avoid packet races, although typically no
> packets would be flowing during that time.
[...]
applied.
johannes
prev parent reply other threads:[~2013-03-04 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 22:19 [PATCH] mac80211: defer tailroom counter manipulation when roaming Johannes Berg
2013-03-04 15:34 ` Johannes Berg [this message]
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=1362411276.21028.24.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=yogeshp@marvell.com \
/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).