From: Johannes Berg <johannes@sipsolutions.net>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: linux-wireless@vger.kernel.org, Kalle Valo <kalle.valo@iki.fi>
Subject: Re: [RFC] Improve software scan timing
Date: Tue, 23 Feb 2010 16:38:13 +0100 [thread overview]
Message-ID: <1266939493.3934.8.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <201002231633.06394.helmut.schaa@googlemail.com>
On Tue, 2010-02-23 at 16:33 +0100, Helmut Schaa wrote:
> > > Kalle, Johannes, how is the listen_interval handled in the
> powersave
> > > code?
> > > Are we only sleeping for one beacon interval or are we ignoring
> the
> > > listen_interval currently.
> >
> > I figured this listen interval stuff would come back to bite us at
> some
> > point. I don't think we should negotiate a listen interval of 1.
> OTOH,
> > I'm not convinced that all APs would reject it with a status code of
> 51
> > if it's too large? Or is that tested anywhere like WFA?
>
> No idea. However for iwlwifi for example we always used a listen
> interval
> of 20 any I never saw any associations getting rejected because of
> this.
>
> So maybe we could just increase the default to something between 5 and
> 10 to be on the safe side?
Yeah, maybe. Could it be useful for userspace to ask for a specific
value with assoc? Though I'm not really sure what it would use ...
johannes
next prev parent reply other threads:[~2010-02-23 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 15:19 [RFC] Improve software scan timing Helmut Schaa
2010-02-23 15:25 ` Johannes Berg
2010-02-23 15:33 ` Helmut Schaa
2010-02-23 15:38 ` Johannes Berg [this message]
2010-02-23 16:44 ` Helmut Schaa
2010-02-23 17:52 ` Johannes Berg
2010-02-23 20:10 ` Helmut Schaa
2010-02-23 19:35 ` Luis R. Rodriguez
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=1266939493.3934.8.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=helmut.schaa@googlemail.com \
--cc=kalle.valo@iki.fi \
--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 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.