From: Ben Greear <greearb@candelatech.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org
Subject: Re: [RFT 0/3] cfg80211: beacon hint improvements
Date: Fri, 14 Dec 2012 10:10:35 -0800 [thread overview]
Message-ID: <50CB6B9B.7020508@candelatech.com> (raw)
In-Reply-To: <1355430534-7881-1-git-send-email-mcgrof@do-not-panic.com>
On 12/13/2012 12:28 PM, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
>
> Just a few improvements for beacon hint processing due to
> scheduling considerations and discovered by Ben with a lot of
> stations. For details see:
I added this and Johannes' station cleanup patches to 3.7 and the
600-station tests are running well so far. I see a few beacon
messages, but no spammage. (I also backed out my rate-limit
patch on the beacon messages, so if they *were* inclined to spam,
I should have seen it).
So:
Tested-by: Ben Greear <greearb@candelatech.com>
Thanks,
Ben
>
> http://article.gmane.org/gmane.linux.kernel.wireless.general/101482
>
> Luis R. Rodriguez (3):
> cfg80211: do not process beacon hints if one is already queued
> cfg80211: move reg_is_world_roaming()
> cfg80211: move world roaming check for beacon hints
>
> net/wireless/reg.c | 48 ++++++++++++++++++++++++++++++++++--------------
> 1 file changed, 34 insertions(+), 14 deletions(-)
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2012-12-14 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 20:28 [RFT 0/3] cfg80211: beacon hint improvements Luis R. Rodriguez
2012-12-13 20:28 ` [RFT 1/3] cfg80211: do not process beacon hints if one is already queued Luis R. Rodriguez
2012-12-13 20:28 ` [RFT 2/3] cfg80211: move reg_is_world_roaming() Luis R. Rodriguez
2012-12-13 20:28 ` [RFT 3/3] cfg80211: move world roaming check for beacon hints Luis R. Rodriguez
2012-12-13 21:23 ` Ben Greear
2012-12-14 18:10 ` Ben Greear [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=50CB6B9B.7020508@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.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).