kfifo_put(9)

📦 version 7.3.1, in nixpkgs unstable

🫶 kfifo_put — the Kernel API Manual, bestie edition 💅

okay so bestie, welcome to kfifo_put(9), straight out of the Kernel API Manual ✨ grab a strawberry 🍓 and let's get into it.

🌸 NAME 🌸

kfifo_put — literally just: put data into the fifo. that's the whole assignment. iconic behavior honestly 👑

✨ SYNOPSIS ✨

kfifo_put (fifo , val );

yes bestie, that comma is doing the most with those spaces, but it's canon, don't touch it 🙈 copy it exactly. periodt.

🎀 ARGUMENTS 🎀

  • fifo — the address of the fifo you're gonna use 💖 this is the main character, point at it correctly or it's giving 💀
  • val — the data you want added in there. the actual payload. the reason we're all here 🦋

🧚 DESCRIPTION 🧚

okay so what this macro does: it copies the given value into the fifo. simple, clean, no cap 💅

then the return value — listen up:

  • it returns 0 if the fifo was full 😭 (tragic, but she's honest about it)
  • otherwise, it returns the number processed elements ✨
🔥 big caveat, do NOT skip this one: with only one concurrent reader and one concurrent writer, you don't need extra locking to use these macro. note that this blessing is conditional — one reader, one writer, that's the vibe check. do not go adding extra readers and writers and expect it to still slay, because the manpage only promised this for that exact setup, fr fr. 🫶

👑 SEE ALSO 👑

the kernel file itself lives at ./include/linux/kfifo.h — go say hi to the source, she has lore 🌈

and there's a whole kfifo friend group, all of them:

like, the whole squad showed up. go read them all, iykyk 📚💜

🦋 so yeah, that's kfifo_put — copies a value in, returns 0 when full, returns processed count otherwise, and only avoids needing locking in that one-reader-one-writer setup. go be a good fifo citizen bestie 🎀

🌸 mwah, this page came from the source path ./include/linux, dated October 2026, and it's kfifo_put(9) — okay bye, ily, drink some water 💖✨🫶

📦 where this page comes from