STRUCT EFX_MAE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 struct efx_mae(9) β€” like, the whole vibe 🌸

okay so bestie, welcome to the Kernel API Manual, section 9, and honestly? we're about to get into the internals of struct efx_mae and it's lowkey iconic. this is the MAE information struct and it's giving "small but mighty" β€” two members, zero fluff, main character energy. πŸ’…


✨ NAME ✨

struct efx_mae β€” MAE information, periodt. that's the whole name. short, sweet, slays.


πŸ¦‹ SYNOPSIS πŸ¦‹

here's the struct in all its glory, copied exactly, no cap:

struct efx_mae {
    struct efx_nic *efx;
    struct rhashtable mports_ht;
 };

look at her. two fields. immaculate. πŸŽ€


πŸ’– Members πŸ’–

okay so let's meet the members one by one, they each have a job and they're both doing it:

  • efx β€” the associated NIC. that's it, that's the field. it's the NIC this whole thing is attached to, the bestie-in-chief, the one it's associated with. 🫢
  • mports_ht β€” m-port descriptions from MC_CMD_MAE_MPORT_READ_JOURNAL. yes, that's the exact command name, i did not touch it, it's a rhashtable holding m-port descriptions that come from that journal read. iykyk. πŸ”₯
ngl, that MC_CMD_MAE_MPORT_READ_JOURNAL name is a whole mouthful but it's literally the source of the m-port descriptions in mports_ht, so we respect it. πŸ‘‘

🌈 SEE ALSO 🌈

  • Kernel file ./drivers/net/ethernet/sfc/mae.h β€” go read it, bestie, that's where all of this actually lives. πŸ“‚βœ¨

and that's the tea! β˜• this page came from ./drivers/net/ethernet/sfc, dated October 2026, and it's struct efx_mae(9) all day every day. go forth and be obsessed with kernel structs, mwah πŸ’œπŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from