handle_outbound(9)

📦 version 7.3.1, in nixpkgs unstable

💅 handle_outbound(9) — a whole moment

okay so bestie, welcome to the Kernel API Manual 🎀 — yes you're reading page handle_outbound(9) from section 9, and honestly? iconic. this is the one about processing filled outbound buffers, and it's lowkey the main character of the outbound side of things. let's get into it 🦋

✨ NAME ✨

handle_outbound — process filled outbound buffers 💖

like, the buffers are already filled, bestie, they're done steeping, and this function handles them. no cap.

🌸 SYNOPSIS 🌸

int handle_outbound (struct qdio_q *q , unsigned int bufnr , unsigned int count , struct qaob *aob );

that's the whole signature, verbatim, don't come for me 🙈 — int in front, four arguments inside, semicolon at the end. slay.

🦋 ARGUMENTS 🦋

  • q — the queue that's holding the buffers. it's a struct qdio_q *, so yes, pointer to a queue struct. this is where the whole vibe lives 👑
  • bufnr — the first buffer to process. not the last, not the middle — the first. unsigned int, keep it that way 💅
  • count — how many buffers are filled. so like, bufnr is where you start and count is how many you're grabbing from there. also unsigned int 🍓
  • aob — the asynchronous operation block, a struct qaob *. it's giving async, it's giving operation block, it's giving what it says on the tin ✨

⭐ SEE ALSO ⭐

okay the cross-reference list is LONG and honestly kind of stunning, so let's give it the respect it deserves 🫶 first up, the kernel file itself: ./drivers/s390/cio/qdio_main.c 🌈 then all these besties:

note the symmetry bestie: handle_inbound(9) is right there next to handle_outbound — inbound and outbound, two sides of the same coin, we love a balanced pair 💜

and that's the page, fr fr 💀 — this little gem comes from ./drivers/s390/cio, stamped October 2026, filed under handle_outbound(9). go forth and process those filled outbound buffers, bestie, you're gonna ate 🔥👑

📦 where this page comes from