mesh_rmc_check(9)
π¦ 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
0if 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 π
- Kernel file
./net/mac80211/mesh.cβ the home base for all of this π mesh_matches_local(9)mesh_peer_accepts_plinks(9)mesh_accept_plinks_update(9)ieee80211_fill_mesh_addresses(9)ieee80211_new_mesh_header(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms