{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifw6lym7tzr6ropnc3eqlufwrj7lsy3rzk2sy4okmmgdsasf6lzkq",
    "uri": "at://did:plc:b3tz6srl4ochk2wxn6dv6xpy/app.bsky.feed.post/3mg4k66rolpu2"
  },
  "path": "/Articles/1060953/",
  "publishedAt": "2026-03-02T20:12:58.000Z",
  "site": "https://lwn.net",
  "tags": [
    "an overview of how zero-copy networking works"
  ],
  "textContent": "Toke Høiland-Jørgensen has posted an overview of how zero-copy networking works in the Linux kernel.\n\n> Since the memory is being copied directly from userspace to the network device, the userspace application has to keep it around unmodified, until it has finished sending. The `sendmsg()` syscall itself is asynchronous, and will return without waiting for this. Instead, once the memory buffers are no longer needed by the stack, the kernel will return a notification to userspace that the buffers can be reused.",
  "title": "Høiland-Jørgensen: The inner workings of TCP zero-copy"
}