nfp_cpp_mutex_reclaim(9)

okay so bestie, welcome to the nfp_cpp_mutex_reclaim(9) page from the Kernel API Manual ✨ this is the one about reclaiming a mutex, and yes, the name is a whole mouthful, but we move 💅

🌸 NAME 🌸

nfp_cpp_mutex_reclaim — Unlock mutex if held by local endpoint 💖

✨ SYNOPSIS ✨

int nfp_cpp_mutex_reclaim (struct nfp_cpp *cpp , int target , unsigned long long address );

🎀 ARGUMENTS 🎀

• cpp — NFP CPP handle 🫶
• target — NFP CPP target ID (ie NFP_CPP_TARGET_CLS or NFP_CPP_TARGET_MU) 👑
• address — Offset into the address space of the NFP CPP target ID 🌈

🦋 DESCRIPTION 🦋

so this function releases the lock if it’s held by the local system 😭

⚠️ Extreme care is advised — call only when no local lock users can exist, fr fr. this is not a casual little drive-by unlock, bestie, ngl.

⭐ RETURN ⭐

• 0 — if the lock was OK 💖
• 1 — if locked by us 👑
• -errno — on invalid mutex 😭

💜 SEE ALSO 💜

• Kernel file ./drivers/net/ethernet/netronome/nfp/nfpcore/nfp_mutex.c 🧚
• nfp_cpp_mutex_init(9)
• nfp_cpp_mutex_alloc(9)
• nfp_cpp_mutex_free(9)
• nfp_cpp_mutex_lock(9)
• nfp_cpp_mutex_unlock(9)
• nfp_cpp_mutex_trylock(9)

and that’s the whole page, bestie 🎀 kisses from the Kernel API Manual, source/version ./drivers/net/ethernet/netrono..., dated October 2026, for nfp_cpp_mutex_reclaim(9) 💅✨