From: <vivekanandah@posedge.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: question on SMPS for AP
Date: Wed, 3 Apr 2013 01:36:20 -0700 [thread overview]
Message-ID: <7a1a483e9382db42e8f648c3933bc2cd@posedge.com> (raw)
In-Reply-To: <1364976319.8351.2.camel@jlt4.sipsolutions.net>
hi Johannes,
thanks for the response.
for the below statement:
Yes this is implemented, it starts in ieee80211_rx_h_action(),
> WLAN_CATEGORY_HT, WLAN_HT_ACTION_SMPS and ends by calling
> rate_control_rate_update(). The driver or rate control algorithm has
> to
> take this into account, I'm not certain that all drivers and
> algorithms
> do this correctly (yet).
i see that the rate_control_rate_update is called with the
IEEE80211_RC_SMPS_CHANGED flag. however, i see that the minstrel_ht code
does not check for SMPS with respect to RTS.
Also, the code - rate_control_rate_update calls - sta_rc_update
mac80211 op. i was first thinking that i could use this for the AP side
notification to driver layer. however, a comment for sta_rc_update
indicates that it is to be used only when IEEE80211_HW_HAS_RATE_CONTROL
is true.
this led to the confusion.
Can this op be used to update the driver about change in station's SMPS
mode for AP ?
thanks and regards
Vivek
On Wed, 03 Apr 2013 10:05:19 +0200, Johannes Berg wrote:
> Hi Vivek,
>
>> i was looking into the MAC80211 code for Spatial multiplexing Power
>> Save handling.
>>
>> i see that for the station side, the code seems to be handled.
>> is the same true for an AP interface as well? this is my current
>> understanding and i do not see any code handling for AP for SMPS.
>
> Which part? There are two sides to SMPS handling:
> 1) changing our own SMPS mode
> 2) handling stations changing their SMPS mode
>
> 1) is implemented only for station mode, 2) is implemented for both
> AP
> and station mode (though is less relevant for station mode)
>
>> From the perspective of an AP, the only thing it needs to do, is to
>> monitor the station for change to dynamic SMPS mode and if the
>> station
>> is in dynamic SMPS mode, set the RTS flag for the first packet to be
>> sent out to the station so that an RTS/CTS mechanism is employed
>> before
>> the packet transfer. this will make the station to wake up its
>> receive
>> chains for the impending packet tranfer.
>>
>> can anyone provide any inputs for the same and direct me to any code
>> that will help in understanding SMPS for AP?
>
> Yes this is implemented, it starts in ieee80211_rx_h_action(),
> WLAN_CATEGORY_HT, WLAN_HT_ACTION_SMPS and ends by calling
> rate_control_rate_update(). The driver or rate control algorithm has
> to
> take this into account, I'm not certain that all drivers and
> algorithms
> do this correctly (yet).
>
> johannes
next prev parent reply other threads:[~2013-04-03 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 7:35 question on SMPS for AP vivekanandah
2013-04-03 8:05 ` Johannes Berg
2013-04-03 8:36 ` vivekanandah [this message]
2013-04-03 8:46 ` Johannes Berg
2013-04-04 6:27 ` RFC: SMPS for AP mode vivekanandah
2013-04-09 10:19 ` Johannes Berg
2013-04-09 15:55 ` Naveenraj Subramanian
[not found] ` <CAGXE3d_Up9BwfR3gC4uDh_4PNfAaMCME7dVeRnNrpmvc70ZALQ@mail.gmail.com>
2013-04-03 8:37 ` question on SMPS for AP vivekanandah
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=7a1a483e9382db42e8f648c3933bc2cd@posedge.com \
--to=vivekanandah@posedge.com \
--cc=johannes@sipsolutions.net \
--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