#2039: Power Save mode Change from Active to Sleep in STA and Pending Transmit
Packets in AP
---------------------------------------------------+------------------------
      Reporter:  [EMAIL PROTECTED]  |       Owner:                              
          Type:  enhancement                       |      Status:  closed       
               
      Priority:  trivial                           |   Milestone:               
               
     Component:  madwifi: driver                   |     Version:  v0.9.4       
               
    Resolution:  invalid                           |    Keywords:  Power Save 
Mode State Change
Patch_attached:  0                                 |  
---------------------------------------------------+------------------------
Changes (by mrenzmann):

  * status:  new => closed
  * resolution:  => invalid

Old description:

> I am currently following madwifi-0.9.4 version.
> I have a general doubt regarding power ssenario here. Proposed situation
> is something like this:
>
> Consider Legacy Power Save support (exclude UAPSD mode for now). AP has
> added data packets for Station A in its Hardware Queue (not yet
> transmitted in Air). '''How will AP handle the case when Station A goes
> into Power Save mode (prior to packets destined for Station A are
> actually transmitted in air).''' Is there any way to check station's
> Power Save mode just before throwing the packet in Air. Or these packets
> are dropped??
>
> ----
>
>    In present madwifi-0.9.4 implementation we check Station's Power Save
> mode in ieee80211_hardstart(skb, dev) function in
> net80211/ieee80211_output.c file. If destined Station is in Power Save
> Mode then data packet is queued in the PS queue of Station, o.w. it is
> given to  ieee80211_parent_queue_xmit(skb) to Kernel API
> dev_queue_xmit(skb) function. dev_queue_xmit handles these packets to
> ath_hardstart(skb, dev) function of parent device in ath/if_ath.c file.
> '''What if station changes its Power Save mode in between i.e., after
> packet is given to ieee80211_parent_queue_xmit but before actually sent
> in Air.''' Actually packet will be added to the corresponding Access
> Category queue, while the destined station is in Sleep State.
>

> ----
>
>    '' Can we minimise this time interval. Like cheking station's Power
> Save status (active/sleep) in ath_hard_start function. Any way once
> packet is added to the Hardware Queues, then we dont have control over
> destined Station's present Sleep state.
> ''''''''

New description:

 I am currently following madwifi-0.9.4 version.

 I have a general doubt regarding power ssenario here. Proposed situation
 is something like this:

 Consider Legacy Power Save support (exclude UAPSD mode for now). AP has
 added data packets for Station A in its Hardware Queue (not yet
 transmitted in Air). '''How will AP handle the case when Station A goes
 into Power Save mode (prior to packets destined for Station A are actually
 transmitted in air).''' Is there any way to check station's Power Save
 mode just before throwing the packet in Air. Or these packets are
 dropped??

 ----

 In present madwifi-0.9.4 implementation we check Station's Power Save mode
 in ieee80211_hardstart(skb, dev) function in net80211/ieee80211_output.c
 file. If destined Station is in Power Save Mode then data packet is queued
 in the PS queue of Station, o.w. it is given to
 ieee80211_parent_queue_xmit(skb) to Kernel API dev_queue_xmit(skb)
 function. dev_queue_xmit handles these packets to ath_hardstart(skb, dev)
 function of parent device in ath/if_ath.c file. '''What if station changes
 its Power Save mode in between i.e., after packet is given to
 ieee80211_parent_queue_xmit but before actually sent in Air.''' Actually
 packet will be added to the corresponding Access Category queue, while the
 destined station is in Sleep State.

 ----

 Can we minimise this time interval. Like cheking station's Power Save
 status (active/sleep) in ath_hard_start function. Any way once packet is
 added to the Hardware Queues, then we dont have control over destined
 Station's present Sleep state.

Comment:

 Please move these questions to the [wiki:Resources#MailingLists madwifi-
 devel] mailing list, as the ticket facility is not the right place for
 such discussions. Thanks.

-- 
Ticket URL: <https://madwifi.org/ticket/2039#comment:1>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets

Reply via email to