mesh_rmc_check(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ mesh_rmc_check(9) β€” the kernel API manual, bestie edition πŸ¦‹

Okay so this is a page from the Kernel API Manual (man section 9, kernel internals, very "I know things" energy) and it's all about mesh_rmc_check. Let's get into it ✨


🌸 NAME 🌸

mesh_rmc_check β€” check a frame in the recent multicast cache and add it if it's absent. That's the whole vibe check in one line, no cap πŸ’…


✨ SYNOPSIS ✨

int mesh_rmc_check (struct ieee80211_sub_if_data *sdata , const u8 *sa ,
       struct ieee80211s_hdr *mesh_hdr );

Look at that signature, she's iconic πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • sdata β€” the interface. Like, the actual wireless sub-if-data situation you're working with 🫢
  • sa β€” the source address. Where the frame says it came from πŸ’Œ
  • mesh_hdr β€” the mesh header. The mesh-y header part, obviously 🌈

πŸ”₯ RETURN πŸ”₯

  • Returns 0 if the frame is not in the cache.
  • Nonzero otherwise (i.e. it was already there, bestie, we've seen this one 🫣).

So yeah: 0 means "new to me", anything else means "already clocked it" ⭐


πŸ’– DESCRIPTION πŸ’–

So here's the tea β˜• β€” this function checks, using the source address and the mesh sequence number, whether we've received this exact frame lately.

If the frame is not in the cache, it gets added to it. Boom, now it's cached. That's literally it and honestly? Slay πŸ’…

It's giving "have I seen this already" energy, but for mesh frames. Main character behavior fr fr 🧚

🌟 SEE ALSO 🌟

All of these are lowkey in the same friend group, go read them too 🫢


Alright bestie, that's the whole page πŸ’œ big kisses from ./net/mac80211, dated October 2026 β€” go forth and cache those frames responsibly πŸŽ€βœ¨

πŸ“¦ where this page comes from