All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Sujith <m.sujith@gmail.com>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	ath9k-devel <ath9k-devel@lists.ath9k.org>,
	Jouni Malinen <j@w1.fi>
Subject: Re: [RFC/WIP 00/33] ath9k_htc AP mode
Date: Sun, 23 Jan 2011 10:11:24 +0100	[thread overview]
Message-ID: <1295773884.3639.9.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <19770.20402.711305.279934@gargle.gargle.HOWL>

On Sat, 2011-01-22 at 09:02 +0530, Sujith wrote:

> It does make it a bit neat to have such a mechanism. And for AP mode, I would think
> that it's kinda essential unless someone comes with an ingenious way of solving
> the PS race for drivers that don't set IEEE80211_HW_REPORTS_TX_ACK_STATUS. :-)

Well, you can handle the PS stuff in the device completely -- or do it
like iwlwifi does, where it doesn't rely on the ACK to detect the race,
but the firmware will reject TX frames to sleeping stations until the
driver tells it the station woke up.

How it works is like this:

STA AWAKE -> ASLEEP transition:
  - firmware marks station as asleep
  - firmware rejects TX frames for this station that are in queue
  - driver keeps track of # of such frames, and uses
    ieee80211_sta_block_awake() to block this station while it has
    frames in the queue
  - rejected frames are rejected to mac80211 and queued up

ASLEEP -> AWAKE:
  - due to ieee80211_sta_block_awake() wakeup is blocked until the
    queue has drained as well (if station very quick wakes up), then
    when both conditions are met,
  - driver tells device that this station woke up
  - mac80211 re-transmits all those frames
  - driver queues up all those frames

johannes


WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC/WIP 00/33] ath9k_htc AP mode
Date: Sun, 23 Jan 2011 10:11:24 +0100	[thread overview]
Message-ID: <1295773884.3639.9.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <19770.20402.711305.279934@gargle.gargle.HOWL>

On Sat, 2011-01-22 at 09:02 +0530, Sujith wrote:

> It does make it a bit neat to have such a mechanism. And for AP mode, I would think
> that it's kinda essential unless someone comes with an ingenious way of solving
> the PS race for drivers that don't set IEEE80211_HW_REPORTS_TX_ACK_STATUS. :-)

Well, you can handle the PS stuff in the device completely -- or do it
like iwlwifi does, where it doesn't rely on the ACK to detect the race,
but the firmware will reject TX frames to sleeping stations until the
driver tells it the station woke up.

How it works is like this:

STA AWAKE -> ASLEEP transition:
  - firmware marks station as asleep
  - firmware rejects TX frames for this station that are in queue
  - driver keeps track of # of such frames, and uses
    ieee80211_sta_block_awake() to block this station while it has
    frames in the queue
  - rejected frames are rejected to mac80211 and queued up

ASLEEP -> AWAKE:
  - due to ieee80211_sta_block_awake() wakeup is blocked until the
    queue has drained as well (if station very quick wakes up), then
    when both conditions are met,
  - driver tells device that this station woke up
  - mac80211 re-transmits all those frames
  - driver queues up all those frames

johannes

  parent reply	other threads:[~2011-01-23  9:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21  2:55 [RFC/WIP 00/33] ath9k_htc AP mode Sujith
2011-01-21  2:55 ` [ath9k-devel] " Sujith
2011-01-21  3:15 ` Sujith
2011-01-21  3:15   ` [ath9k-devel] " Sujith
2011-01-21 21:26 ` Christian Lamparter
2011-01-21 21:26   ` [ath9k-devel] " Christian Lamparter
2011-01-22  2:56   ` Sujith
2011-01-22  2:56     ` [ath9k-devel] " Sujith
2011-01-22  2:57     ` Sujith
2011-01-22  3:32       ` Sujith
2011-01-22  3:32         ` [ath9k-devel] " Sujith
2011-01-22 12:48         ` Christian Lamparter
2011-01-22 12:48           ` [ath9k-devel] " Christian Lamparter
2011-01-22 16:58           ` Sujith
2011-01-22 16:58             ` [ath9k-devel] " Sujith
2011-01-23  9:11         ` Johannes Berg [this message]
2011-01-23  9:11           ` Johannes Berg
2011-01-23 10:01           ` Sujith
2011-01-23 10:01             ` [ath9k-devel] " Sujith
2011-01-23 10:05             ` Johannes Berg
2011-01-23 10:05               ` [ath9k-devel] " Johannes Berg

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=1295773884.3639.9.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=chunkeey@googlemail.com \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=m.sujith@gmail.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.