nfp_cpp_mutex_alloc(9)

📦 version 7.3.1, in nixpkgs unstable

✨ nfp_cpp_mutex_alloc(9) ✨

okay so bestie, welcome to the Kernel API Manual entry for nfp_cpp_mutex_alloc(9) — this is the glow-up guide to making a mutex handle and honestly it's giving "small function, big responsibility" 💅

💖 NAME 💖

nfp_cpp_mutex_alloc — Create a mutex handle 🎀

🌸 SYNOPSIS 🌸

struct nfp_cpp_mutex * nfp_cpp_mutex_alloc (struct nfp_cpp *cpp , int
target , unsigned long long address , u32 key );

like, that's the whole signature, no cap. four args, one struct pointer back. slay.

🦋 ARGUMENTS 🦋

  • cpp — the NFP CPP handle 💜 like, your main character context object, you literally cannot do this without it
  • target — the NFP CPP target ID (ie NFP_CPP_TARGET_CLS or NFP_CPP_TARGET_MU) ✨ so you gotta say where you're pointing, bestie
  • address — offset into the address space of the NFP CPP target ID 📍 it's a location, not a vibe
  • key — a 32-bit unique key (must match the key at this location) 🔑 and yeah, it must match the key already sitting at that location, no faking it

🧚 DESCRIPTION 🧚

okay so here's the tea 🍓: the CPP target:address must point to a 64-bit aligned location, and you gotta reserve 64 bits of data at that location for use by the handle. like actually reserve them, don't be messy about it 🙈

and ngl, only target/address pairs that point to entities supporting the MU Atomic Engine's CmpAndSwap32 command are supported. so if your pair doesn't support that, it's simply not the moment 💀 no exceptions, that's just the rules.

👑 RETURN 👑

  • A non-NULL struct nfp_cpp_mutex * on success 🎉
  • NULL on failure 😭 (she's not mad, she's just disappointed)

🔥 SEE ALSO 🔥

kk that's the whole page bestie, go forth and allocate responsibly 🫶

source: ./drivers/net/ethernet/netrono... ⭐ version date: October 2026 — mwah, that's the sign-off, nfp_cpp_mutex_alloc(9) out 💜💅

📦 where this page comes from