p9_virtio_zc_request(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… p9_virtio_zc_request πŸ’…

okay so bestie, welcome to the Kernel API Manual ✨ β€” this little cutie lives in p9_virtio_zc_request(9) and honestly? it's giving zero copy realness. let's get into it 🫢


✨ NAME ✨

p9_virtio_zc_request β€” issue a zero copy request πŸ’«

like, the whole point is you're issuing a request and nobody's copying your buffers around. iconic behavior only πŸ‘‘


🌸 SYNOPSIS 🌸

int p9_virtio_zc_request (struct p9_client *client , struct p9_req_t
*req , struct iov_iter *uidata , struct iov_iter *uodata , int inlen ,
int outlen , int in_hdr_len );

copy it exactly, bestie, don't be cute with it 😭


πŸŽ€ ARGUMENTS πŸŽ€

  • client β€” the client instance that's issuing the request. main character of this whole operation fr fr πŸ’–
  • req β€” the request that's actually getting issued. yes, this one, the one you brought πŸ¦‹
  • uidata β€” user buffer that should be used for zero copy read πŸ‘€βœ¨ no copying, we said what we said
  • uodata β€” user buffer that should be used for zero copy write βœοΈπŸ’« also no copying, keep up
  • inlen β€” read buffer size. the length of the read situation πŸ“
  • outlen β€” write buffer size. the length of the write situation πŸ“
  • in_hdr_len β€” reader header size; this is the size of the response protocol data 🧚 lowkey important, don't skip it

🌈 SEE ALSO 🌈

like a little friend group of functions, we love a linked list of besties πŸ«ΆπŸ’œ


ngl bestie, this page is short and sweet β€” but every arg matters, so don't go forgetting your in_hdr_len on the way out πŸ™ˆ

and that's the whole vibe check πŸ’… this one's from ./net/9p, dated October 2026, and it's filed right back under p9_virtio_zc_request(9) β€” periodt πŸŽ€βœ¨πŸŒΈ

πŸ“¦ where this page comes from