vringh_iov_push_user(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vringh_iov_push_user πŸ’…

okay so bestie, welcome to the Kernel API Manual ✨ this one's a little function from the vhost/vringh corner of the kernel and honestly? she's a whole vibe. let's get into it 🫢


✨ NAME ✨

vringh_iov_push_user β€” literally copies bytes into a vring_iov. that's the whole job. main character energy, minimal dramatics πŸŽ€


🌸 SYNOPSIS 🌸

ssize_t vringh_iov_push_user (struct vringh_iov *wiov , const void *src
, size_t len );

ngl the signature is giving "three args and a dream" πŸ’€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • wiov β€” the wiov as passed to vringh_getdesc_user (updated as we consume). yes bestie, it gets mutated in place as the function eats through it, so don't act surprised πŸ‘€
  • src β€” the place to copy from. your source. your origin story πŸ’–
  • len β€” the maximum length to copy. emphasis on maximum, she will not overshoot πŸ”₯

⭐ DESCRIPTION ⭐

Returns the bytes copied <= len or a negative errno. that's it, that's the paragraph 😭 so like β€” you get back a count that is less than or equal to len, OR you get a negative errno if things went sideways. slay either way πŸ’…


🌈 SEE ALSO 🌈

the whole fam, no cap β€” this list is long and every single one of them stays:

like I said. the whole fam. iykyk 🧚


aaaand that's the page!! πŸ“ this lil icon lives in ./drivers/vhost and the docs are dated October 2026 β€” so like, future-coded of them tbh πŸ’œ go push some bytes bestie, you got this βœ¨πŸ’…

πŸ“¦ where this page comes from