memcpy_toio(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… memcpy_toio β€” a kernel API manual moment, bestie ✨

okay so picture this: it's giving Kernel API Manual, it's giving memcpy_toio(9), and it's literally the function you call when you need bytes to go into I/O memory. sit down, hydrate, let's get into it 🫢


🌸 NAME 🌸

memcpy_toio β€” copy a block of data into I/O memory. that's it. that's the whole vibe. no cap πŸ’–


✨ SYNOPSIS ✨

void memcpy_toio (volatile void __iomem *dst , const void *src , size_t
count );

look at her. three args, no return value, absolutely unbothered. she's a void girlie and she knows it πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dst β€” the destination for the copy, and it's I/O memory, bestie. note the volatile void __iomem * energy β€” this is not your regular RAM, this is the fancy address space πŸ’…
  • src β€” the source of the data, and this one is RAM. regular degular memory. iconic of it honestly 🌈
  • count β€” the number of bytes to copy. yes, bytes. count them. be precise. slay ⭐

πŸ”₯ DESCRIPTION πŸ”₯

Copy a block of data to I/O memory.

that's the whole description and honestly? she said what she said. no notes. periodt πŸ’€βœ¨


πŸ‘‘ SEE ALSO πŸ‘‘

the whole iomem copy friend group!! go say hi to the other two, they're literally right there πŸ§šπŸ’œ


fr fr though: this is the "to I/O" direction. if you wanted data coming out of I/O memory, that's memcpy_fromio(9), and if you're setting instead of copying, that's memset_io(9). iykyk πŸ˜­πŸ¦‹

and that's the page!! source/version: ./lib, dated October 2026, manual memcpy_toio(9) β€” mwah, go copy some bytes responsibly, bestie πŸ’–πŸŽ€πŸ’…

πŸ“¦ where this page comes from