From: Johannes Berg <johannes@sipsolutions.net>
To: greearb@candelatech.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] mac80211: Make beacon-loss-count configurable.
Date: Fri, 22 Mar 2013 11:31:31 +0100 [thread overview]
Message-ID: <1363948291.8238.10.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1363727997-1554-1-git-send-email-greearb@candelatech.com> (sfid-20130319_222010_382492_3F895FA6)
On Tue, 2013-03-19 at 14:19 -0700, greearb@candelatech.com wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> On loaded systems with lots of VIFs, I see lots of beacon
> timeouts, even though the connection to the AP is very
> good. Allow tuning the beacon-loss-count variable to
> give the system longer to process beacons if the user
> prefers.
Applied, I also added the number to the message, just in case somebody
sets it to 0 or 1 or something like that ... :-)
johannes
prev parent reply other threads:[~2013-03-22 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 21:19 [PATCH 1/2] mac80211: Make beacon-loss-count configurable greearb
2013-03-19 21:19 ` [PATCH 2/2] mac80211: Make un-found-rate splat a warn-once greearb
2013-03-22 10:28 ` Johannes Berg
2013-03-22 15:59 ` Ben Greear
2013-04-03 12:41 ` Johannes Berg
2013-03-22 10:31 ` 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=1363948291.8238.10.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--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).