ieee80211_mps_frame_release(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ieee80211_mps_frame_release(9)

okay so this is a Kernel API Manual page, and bestie, we're talking about mesh power save and how buffered frames finally get released ✨


🌸 NAME 🌸

ieee80211_mps_frame_release β€” the function that releases frames that were buffered because of mesh power save πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

void ieee80211_mps_frame_release (struct sta_info *sta , struct
ieee802_11_elems *elems );

πŸ’– ARGUMENTS πŸ’–

  • sta β€” the mesh STA πŸ‘‘ (that's the station we're doing all this for)
  • elems β€” the IEs from a beacon or probe response 🧚 (yep, the information elements, freshly parsed)

πŸ”₯ DESCRIPTION πŸ”₯

okay so for peers: if we've got individually-addressed frames buffered, or the peer is telling us it has buffered frames, we send a corresponding MPSP trigger frame. periodt πŸ’…

and here's the little detail β€” since we do not evaluate the awake window duration (like, at all, we're not even looking at it πŸ™ˆ), QoS Nulls are what get used as MPSP trigger frames. that's the move.

if the neighbour STA isn't a peer? then we only send single frames. no trigger frame energy for non-peers, that's the rule 🌈


⭐ SEE ALSO ⭐


ngl bestie, if you're digging into mesh_ps.c you're gonna want all of those β€” they're the whole mesh power save friend group and they slay together 🫢

and that's the whole page!! πŸ“ this one lives in ./net/mac80211 and it's dated October 2026 β€” so like, future vibes only πŸ’œ bye bestie, go release those frames πŸ˜­πŸ’–

πŸ“¦ where this page comes from