Reduce Wireless Management Traffic: Difference between revisions
Jump to navigation
Jump to search
(New page: This page is the action page for recommendation [http://wiki.laptop.org/go/Wireless_Recommendations#I2._Reduce_the_management_traffic I2]. Based on the analysis detailed on [http://wiki.l...) |
No edit summary |
||
| Line 3: | Line 3: | ||
Based on the analysis detailed on [http://wiki.laptop.org/go/Wireless_Management_Traffic the Wireless Management Traffic page], we recommend that: |
Based on the analysis detailed on [http://wiki.laptop.org/go/Wireless_Management_Traffic the Wireless Management Traffic page], we recommend that: |
||
* Action 1: Reduce the beacon frequency <trac>7900</trac> |
|||
| ⚫ | |||
The beacon frequency should be reduced from its current default value of 10Hz to 1Hz. |
|||
Pros: This will save a significant amount of airtime, see [http://wiki.laptop.org/go/Wireless_Management_Traffic the Wireless Management Traffic page] for analysis. |
|||
Attention: This will impact current contention window adaptation logic that expects the beacon frequency to be 10Hz. |
|||
'''TICKET:''' |
|||
Task list: |
|||
# Marvell: please comment on the contention window adaptation logic, confirming or not that , and proposing a solution (new firmaware release?) |
|||
# Cozybit: please clarify if the default value is set on the driver |
|||
| ⚫ | |||
XOs should send out probe requests less frequently |
|||
Revision as of 19:01, 9 August 2008
This page is the action page for recommendation I2.
Based on the analysis detailed on the Wireless Management Traffic page, we recommend that:
- Action 1: Reduce the beacon frequency <trac>7900</trac>
- Action 2: Reduce probe request frequency and probe response retry number