qman_retire_fq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay bestie, welcome to qman_retire_fq(9) from the Kernel API Manual πŸ’–

qman_retire_fq β€” Retires a FQ. That’s the whole vibe. πŸ‘‘


🫢 SYNOPSIS 🫢

int qman_retire_fq (struct qman_fq *fq , u32 *flags );

πŸŽ€ ARGUMENTS πŸŽ€

  • fq β€” the frame queue object to retire, aka the main character getting its retirement arc 🌸
  • flags β€” FQ flags (QMAN_FQ_STATE*) if retirement completes immediately ✨

πŸ”₯ DESCRIPTION πŸ”₯

Retires the frame queue. This returns zero if it succeeds immediately, +1 if the retirement was started asynchronously, otherwise it returns negative for failure. No cap, that’s the whole return-value situation πŸ’…

When this function returns zero, flags is set to indicate whether the retired FQ is empty and/or whether it has any ORL fragments (to show up as ERNs). Otherwise the corresponding flags will be known when a subsequent FQRN message shows up on the portal's message ring. πŸŒ€

NB, if the retirement is asynchronous (the FQ was in the Truly Scheduled or Active state), the completion will be via the message ring as a FQRN β€” but the corresponding callback may occur before this function returns!! Ie. the caller should be prepared to accept the callback as the function is called, not only once it has returned. 😭 This is not a drill, bestie β€” be ready early. 🚨

🌈 SEE ALSO 🌈

Kernel file ./include/soc/fsl/qman.h and all these function besties πŸ‘‘:


mwah πŸ’‹ β€” source/version is ./include/soc/fsl, dated October 2026. slay, go read those refs 🫢

πŸ“¦ where this page comes from