async_memcpy(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… async_memcpy β€” bestie, it's a kernel API manual page (section 9, from the Kernel API Manual, and yes she's that girl)

okay so imagine you want to copy some memory but you're too important to do it yourself, so you ask a dma engine to handle it πŸ’β€β™€οΈ that's the whole vibe of async_memcpy. it attempts the copy. no promises, no cap.


✨ SYNOPSIS ✨

struct dma_async_tx_descriptor * async_memcpy (struct page *dest ,
       struct page *src , unsigned int dest_offset , unsigned int src_offset ,
       size_t len , struct async_submit_ctl *submit );

look at her go 😭 six whole arguments, main character energy fr fr. she hands you back a struct dma_async_tx_descriptor * β€” that's the transaction descriptor, keep it safe 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • dest β€” the destination page. this is where the copy lands, the moment of truth πŸ’–
  • src β€” the src page. yeah, just src, she's giving minimal effort and honestly? iconic.
  • dest_offset β€” offset into dest to start transaction. like, which byte in dest we're kicking things off at ⭐
  • src_offset β€” offset into src to start transaction. same deal but for src, you got this 🌸
  • len β€” length in bytes. how much we're copying, literally the size of the vibe πŸ¦‹
  • submit β€” submission / completion modifiers. this is where you whisper your settings to her πŸ‘€

πŸ”₯ DESCRIPTION πŸ”₯

honored flags: ASYNC_TX_ACK β€” that's the one, that's the only one she honors πŸ’… (iykyk)

ngl bestie, the description is short here. honored flags: ASYNC_TX_ACK. that's the entire description. do not go looking for ✨more✨, there is no more. periodt.

🌈 SEE ALSO 🌈

  • Kernel file ./crypto/async_tx/async_memcpy.c β€” go read the source, she's literally right there 🧚

and that's the page!! πŸ’œ this little beauty lives in ./crypto/async_tx, dated October 2026, and she answers to the name async_memcpy(9) β€” mwah, slay, go copy some memory safely bestie πŸŽ€βœ¨

πŸ“¦ where this page comes from