Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@adurom.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	Paul Stewart <pstew@google.com>,
	Amod Bodas <amod.bodas@atheros.com>
Subject: Re: [PATCH 08/10] mac80211: send last 3/5 probe requests as unicast
Date: Wed, 15 Sep 2010 01:12:11 +0300	[thread overview]
Message-ID: <87mxrk5610.fsf@purkki.adurom.net> (raw)
In-Reply-To: <1284474071-8404-1-git-send-email-lrodriguez@atheros.com> (Luis R. Rodriguez's message of "Tue\, 14 Sep 2010 10\:21\:11 -0400")

"Luis R. Rodriguez" <lrodriguez@atheros.com> writes:

> We need to do this since the beacon monitor does not
> push back the connection monitor by design so even if we
> are getting beacons from these type of APs our connection
> monitor currently relies heavily on the way the probe
> requests are received on the AP. An example of an AP
> affected by this is the Nexus One, but this has also been
> observed with random APs.
>
> We can probably optimize this later by using null funcs
> instead of probe requests.

Beginning of this year I sent patches to use null funcs. Unfortunately
I had to drop them due to time constraints.

Also a major power consumption imporovement from using null func
frames is that we don't have to trigger dynamic power save timer
during the poll. Just send the frame with PSM bit set, wait for ack
and go immeaditely back to sleep. So instead of having radios enabled
for example 100 ms per frame, we can do it in just 1 ms.

-- 
Kalle Valo

  reply	other threads:[~2010-09-14 22:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14 14:21 [PATCH 08/10] mac80211: send last 3/5 probe requests as unicast Luis R. Rodriguez
2010-09-14 22:12 ` Kalle Valo [this message]
2010-09-14 22:15   ` Luis R. Rodriguez
2010-09-14 22:21     ` Kalle Valo

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=87mxrk5610.fsf@purkki.adurom.net \
    --to=kvalo@adurom.com \
    --cc=amod.bodas@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=pstew@google.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