qdio_add_buf..._input_queue(9)

📦 version 7.3.1, in nixpkgs unstable

💖 qdio_add_buf..._input_queue(9) 💖

okay so bestie, welcome to the Kernel API Manual ✨ — this is the page for qdio_add_buf..._input_queue(9), and yes the title really does have that lil "..." in the middle, no cap, we don't make the rules 🎀

✨ NAME ✨

qdio_add_bufs_to_input_queue — the one that processes buffers on an Input Queue 🦋

🌸 SYNOPSIS 🌸

int qdio_add_bufs_to_input_queue (struct ccw_device *cdev , unsigned int
q_nr , unsigned int bufnr , unsigned int count );

like, that's the whole vibe: you give it a device, a queue, a starting buffer and a count, and it goes to work 💅

🎀 ARGUMENTS 🎀

  • cdev — the associated ccw_device for the qdio subchannel, i.e. the main character of this whole operation 👑
  • q_nr — queue number, so it knows which queue we're talking about 🔢
  • bufnr — buffer number, the exact spot where the processing starts 📍
  • count — how many buffers to process, like literally how many, don't skip any 🙈

🌈 SEE ALSO 🌈

okay this is the friend group, pay attention 👯‍♀️ the Kernel file is ./drivers/s390/cio/qdio_main.c, and the whole squad is:

like, the range 💀 from allocate to shutdown, the way this lineup ate 🔥 iykyk

ngl bestie, that's genuinely everything this page says — no hidden lore, no extra flags, just the name, the signature, the four arguments and the whole adorable little family of related calls 🫶

✨ sign-off time ✨ this icon lives in ./drivers/s390/cio, dated October 2026, and it slays every single day 💜 bye bestie, go process those buffers 🧚‍♀️💅

📦 where this page comes from