All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] mac80211:  Make some mlme timers module paramaters.
Date: Mon, 14 Feb 2011 07:34:58 -0800	[thread overview]
Message-ID: <4D594BA2.5080905@candelatech.com> (raw)
In-Reply-To: <1297685561.3785.36.camel@jlt3.sipsolutions.net>

On 02/14/2011 04:12 AM, Johannes Berg wrote:
> On Fri, 2011-02-04 at 15:30 -0800, greearb@candelatech.com wrote:
>> From: Ben Greear<greearb@candelatech.com>
>>
>> This allows users to tune the connection-loss algorithms
>> to be more or less lenient.  In particular, larger
>> null-func retries helps when using lots of virtual
>> stations on a loaded network.
>
> I see this has been merged, but I really think it should be reverted. It
> doesn't really fix anything, and it makes the behaviour less
> predictable. Also, even on a loaded network the nullfunc frames should
> be transmitted quickly as they go out on VO. I'm thinking the fact that
> it doesn't will also affect other things -- like the bufferbloat
> discussion -- and fixing the problem would be a much better idea.

The defaults stay the same, and allowing the values to be set a bit larger
lets 128 stations associate, where without this, they constantly fail the
null-func retries counter.

Imagine 128 stations all trying to associate and auth WPA at the
same time, and start DHCP and some IPv6 auto-negotiation
as soon as they are up...  That is quite a lot of packets
for a bunch of timing-sensitive operations.

I know my particular use is pretty strange, but surely I'm not
the only one that would like a good way to stress-test APs.

I can also imagine that other users might like their system even more
trigger happy..perhaps that would speed up roaming in some cases.
Or users on very poor/congested networks, flakey APs, etc.

The default values seem to be chosen arbitrarily to work for most
users most of the time.  I think it adds way more benefit to allow
these easily changed than any harm that comes from giving users
the option.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2011-02-14 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 23:30 [PATCH] mac80211: Make some mlme timers module paramaters greearb
2011-02-14 12:12 ` Johannes Berg
2011-02-14 15:34   ` Ben Greear [this message]
2011-02-14 17:06     ` Sam Leffler

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=4D594BA2.5080905@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.