qman_destroy_fq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– qman_destroy_fq β€” the Kernel API Manual glow-up ✨

okay bestie, gather round, because we're talking about qman_destroy_fq from the Kernel API Manual (section 9, obviously β€” kernel stuff only πŸ’…). This is the page where you learn how to politely hand a frame queue back and reclaim ownership of its memory. Let's get into it πŸŽ€


✨ NAME ✨

qman_destroy_fq β€” literally just deallocates a FQ, that's the whole vibe πŸ¦‹


🌸 SYNOPSIS 🌸

void qman_destroy_fq (struct qman_fq *fq );

no cap, that's the entire signature. clean, simple, iconic.


🫢 ARGUMENTS 🫢

  • fq β€” the frame queue object you're releasing, bestie. that's the one you want to let go of πŸ’–

πŸ’… DESCRIPTION πŸ’…

so here's the tea β˜•: the memory for this frame queue object β€” the fq you handed in to qman_create_fq β€” does not get deallocated by this call. nope! instead, you, the caller, regain ownership of it, and you can do with it as you desire. it's giving "here you go bestie, it's yours now" 🎁

⚠️ but listen β€” there's a vibe check. the FQ must be in the 'out-of-service' state or in the 'parked' state. don't come at this function with an FQ in any other state, fr fr. that's the rule, periodt. πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

and now the whole squad 🌈 β€” the kernel file ./include/soc/fsl/qman.h, plus all these iconic siblings:


and that's the whole page, bestie 🧚 this lil gem lives in ./include/soc/fsl, dated October 2026, and it's brought to you straight from the Kernel API Manual. mwah πŸ’‹ slay, stay parked, and see you in the next manpage ✨πŸ”₯

πŸ“¦ where this page comes from