NE_ERR_MEM_D...NT_NUMA_NODE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NE_ERR_MEM_DIFFERENT_NUMA_NODE(9) β€” like, the Kernel API Manual one, bestie πŸŽ€

okay so picture this: it's a page from the Kernel API Manual and it's all about one (1) extremely specific error code. she's niche, she's iconic, and honestly? she ate. let's get into it ✨


✨ NAME ✨

NE_ERR_MEM_DIFFERENT_NUMA_NODE β€” the user space memory region is backed by pages from different NUMA nodes than the CPUs. 🫢

like literally. your memory is hanging out on one node and your CPUs are living their best life on another. different zip codes. not the vibe check we were hoping for πŸ’€


πŸ¦‹ SYNOPSIS πŸ¦‹

NE_ERR_MEM_DIFFERENT_NUMA_NODE

no arguments, no parameters, no little friends β€” just the code itself, standing there being a whole error πŸ’…


🌈 SEE ALSO 🌈

the full friend group, no gatekeeping, iykyk πŸ‘‘

  • the Kernel file ./include/uapi/linux/nitro_enclaves.h
  • Nitro Enclaves (NE) Kernel Driver Interface(9)
  • NE_CREATE_VM(9)
  • NE_ADD_VCPU(9)
  • NE_GET_IMAGE_LOAD_INFO(9)
  • NE_SET_USER_MEMORY_REGION(9)
  • NE_START_ENCLAVE(9)
  • NE specific error codes(9) β€” the mothership, start here fr fr ⭐
  • NE_ERR_VCPU_ALREADY_USED(9)
  • NE_ERR_VCPU_NOT_IN_CPU_POOL(9)
  • NE_ERR_VCPU_INVALID_CPU_CORE(9)
  • NE_ERR_INVALID_MEM_REGION_SIZE(9)
  • NE_ERR_INVALID_MEM_REGION_ADDR(9)
  • NE_ERR_UNALIGNED_MEM_REGION_ADDR(9)
  • NE_ERR_MEM_REGION_ALREADY_USED(9)
  • NE_ERR_MEM_NOT_HUGE_PAGE(9)
  • NE_ERR_MEM_MAX_REGIONS(9)
  • NE_ERR_NO_MEM_REGIONS_ADDED(9)
  • NE_ERR_NO_VCPUS_ADDED(9)
  • NE_ERR_ENCLAVE_MEM_MIN_SIZE(9)
  • NE_ERR_FULL_CORES_NOT_USED(9)
  • NE_ERR_NOT_IN_INIT_STATE(9)
  • NE_ERR_INVALID_VCPU(9)
  • NE_ERR_NO_CPUS_AVAIL_IN_POOL(9)
  • NE_ERR_INVALID_PAGE_SIZE(9)
  • NE_ERR_INVALID_FLAG_VALUE(9)
  • NE_ERR_INVALID_ENCLAVE_CID(9)
  • Image load info flags(9)
  • NE_EIF_IMAGE(9)
  • struct ne_image_load_info(9)
  • User memory region flags(9)
  • NE_DEFAULT_MEMORY_REGION(9)
  • struct ne_user_memory_region(9)
  • Enclave start info flags(9)
  • NE_ENCLAVE_PRODUCTION_MODE(9)
  • NE_ENCLAVE_DEBUG_MODE(9)
  • struct ne_enclave_start_info(9)

ok but seriously bestie β€” if you're hitting this one, your pages and your CPUs are living on different NUMA nodes. that's the whole entire error. no cap πŸ”₯

mwah, that's the page! 🧚 source lives at ./include/uapi/linux, dated October 2026, and the manual section is NE_ERR_MEM_D...NT_NUMA_NODE(9) β€” go forth and keep your memory and your CPUs on the same node, bestie, love u πŸ’–πŸŒΈ

πŸ“¦ where this page comes from