Page MenuHomeFreeBSD

net80211: update ieee80211_node_get_txrate_mbit() to support VHT
ClosedPublic

Authored by adrian on Jan 23 2025, 2:44 AM.
Referenced Files
F170054279: D48613.id149907.diff
Thu, Sep 3, 9:22 AM
F170005985: D48613.id150011.diff
Thu, Sep 3, 5:52 AM
F169997582: D48613.id150938.diff
Thu, Sep 3, 5:27 AM
F169993198: D48613.id151532.diff
Thu, Sep 3, 5:13 AM
F169986823: D48613.id149744.diff
Thu, Sep 3, 4:51 AM
F169985402: D48613.id150157.diff
Thu, Sep 3, 4:45 AM
F169964930: D48613.id151096.diff
Thu, Sep 3, 3:11 AM
F169885709: D48613.id149855.diff
Wed, Sep 2, 9:26 PM

Details

Summary

Update ieee80211_node_get_txrate_mbit() to use
ieee80211_phy_vht_get_mcs_kbit() to calculate VHT rates.

For now just assume long-GI; I'd have to go and do some extra
work to figure out which short/long GI flag to use.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 62411
Build 59295: arc lint + arc unit

Event Timeline

This revision is now accepted and ready to land.Jan 28 2025, 10:00 AM
This revision now requires review to proceed.Jan 30 2025, 5:15 AM
bz requested changes to this revision.Feb 22 2025, 11:11 AM
bz added a subscriber: bz.

The commit message already talks about the wrong function (kbit ot mbit).

sys/net80211/ieee80211_node.c
3317

Why not just add the checks for 80/160 and pass the bool accordingly rather than leaving a comment no one will find again the next 10 years? We don't have a ni_flag for it but it's in the iv/ni_vhtcap and probably not duplicating the information but having an accessor function would be a lot better and less confusing anyway.

This revision now requires changes to proceed.Feb 22 2025, 11:11 AM
sys/net80211/ieee80211_node.c
3317

heh. fine. :-)

I'm happy to take on a task to clean this up once the diff stack lands. I don't wanna try and insert some more commits into this already big diff stack.

I'll take a TODO to write an analogue to the HT shortgi methods, and also write a HT one that takes a bandwidth as well to clean that API up.

This revision was not accepted when it landed; it landed in state Needs Revision.Feb 26 2025, 7:32 PM
This revision was automatically updated to reflect the committed changes.