qi_cache_free(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– qi_cache_free πŸ’–

okay bestie, welcome to the Kernel API Manual entry for qi_cache_free β€” yes, it's giving kernel cleanup realness, and we're gonna get through it together. 🫢✨


✨ NAME ✨

qi_cache_free β€” frees buffers allocated from CAAM-QI cache</p>. That's the whole gig, no cap. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

void qi_cache_free (void *obj );

πŸŽ€ ARGUMENTS πŸŽ€

  • obj β€” the object that was previously allocated using qi_cache_alloc. Basically: the thing you got from qi_cache_alloc earlier, now ready for its cleanup moment. 🌸

πŸ’… DESCRIPTION πŸ’…

So this gets invoked when a user of the CAAM-QI (i.e. caamalg-qi) no longer needs the buffer that was previously allocated by a qi_cache_alloc call. It's the "we're done with this buffer now" call. 🧚

🚨 No checking is being done β€” like, none. The call is a passthrough call to kmem_cache_free(...). Periodt. πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

Kernel file: ./drivers/crypto/caam/qi.h

Also go peek at these icons: caam_drv_ctx_init(9), caam_qi_enqueue(9), caam_drv_ctx_busy(9), caam_drv_ctx_update(9), caam_drv_ctx_rel(9), and qi_cache_alloc(9). πŸ‘‘


xoxo, your kernel bestie πŸ’‹ β€” this page comes from ./drivers/crypto/caam and is dated October 2026. 🌈⭐

πŸ“¦ where this page comes from