Page MenuHomeFreeBSD

rum(4): fix stats interpretation in rum_ratectl_task()
ClosedPublic

Authored by avos on Sep 17 2015, 3:02 PM.
Tags
None
Referenced Files
Unknown Object (File)
Oct 17 2024, 11:52 AM
Unknown Object (File)
Oct 17 2024, 11:52 AM
Unknown Object (File)
Oct 17 2024, 11:29 AM
Unknown Object (File)
Oct 4 2024, 1:35 PM
Unknown Object (File)
Oct 2 2024, 8:26 AM
Unknown Object (File)
Oct 1 2024, 5:49 AM
Unknown Object (File)
Oct 1 2024, 2:05 AM
Unknown Object (File)
Sep 28 2024, 12:33 AM
Subscribers

Details

Test Plan

Tested on WUSB54GC, STA mode

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

avos retitled this revision from to rum(4): fix stats interpretation in rum_ratectl_task().
avos updated this object.
avos edited the test plan for this revision. (Show Details)
avos set the repository for this revision to rS FreeBSD src repository - subversion.

hi,

Just a note - when you change hardware stuff like this, can you please include where you're sourcing things like register changes, usage, etc?

In D3690#78165, @adrian wrote:

hi,

Just a note - when you change hardware stuff like this, can you please include where you're sourcing things like register changes, usage, etc?

Yes:

  1. http://mirror.robert-marquardt.com/downloads/DSRT2571W_V3-1.3_062207.pdf
  2. manual testing:
    • print all statistic values from rum_ratectl_task() (every second);
    • and, then, test it with:

a) ifconfig wlan1 maxretry 0;
b) ifconfig wlan1 maxretry 1;
c) ifconfig wlan1 maxretry 2;
d) ifconfig wlan1 maxretry 9;
(note: you must merge D3689 before trying to set maxretry parameter)
+ monitor all traffic & compare results.

This revision was automatically updated to reflect the committed changes.