NE_SEND_DATA(9)

💅 NE_SEND_DATA 💅

okay so bestie, this page is from the Kernel API Manual, and it’s about one very specific little buffer. NE_SEND_DATA is that girl. She’s not complicated, she’s just 240 bytes of send-buffer realness, and the Read/Write energy is very much giving “you can look, and you can write.” 💖

💖 NAME 💖

NE_SEND_DATA is the buffer of 240 bytes for sending the command request payload — Read/Write, no cap. It’s literally the outbox for command request payloads, and yes, she is iconic for that. ✨

✨ SYNOPSIS ✨

the whole synopsis is just this, bestie — no extra flags, no side quests:

NE_SEND_DATA

🦋 SEE ALSO 🦋

bestie, the cross-reference list ate and left no crumbs. Every single one is here, so go read up iykyk:

• Kernel file ./drivers/virt/nitro_enclaves/ne_pci_dev.h
• Nitro Enclaves (NE) PCI device(9)
• PCI_DEVICE_ID_NE(9)
• PCI_BAR_NE(9)
• Device registers in the NE PCI device MMIO BAR(9)
• NE_ENABLE(9)
• NE_VERSION(9)
• NE_COMMAND(9)
• NE_EVTCNT(9)
• NE_RECV_DATA(9)
• Device MMIO buffer sizes(9)
• NE_SEND_DATA_SIZE(9)
• NE_RECV_DATA_SIZE(9)
• MSI-X interrupt vectors(9)
• NE_VEC_REPLY(9)
• NE_VEC_EVENT(9)
• enum ne_pci_dev_cmd_type(9)
• Device commands - payload structure for requests and replies.(9)
• struct enclave_start_req(9)
• struct enclave_get_slot_req(9)
• struct enclave_stop_req(9)
• struct slot_alloc_req(9)
• struct slot_free_req(9)
• struct slot_add_mem_req(9)
• struct slot_add_vcpu_req(9)
• struct slot_count_req(9)
• struct next_slot_req(9)
• struct slot_info_req(9)
• struct slot_add_bulk_vcpus_req(9)
• struct ne_pci_dev_cmd_reply(9)
• struct ne_pci_dev(9)
• ne_do_request(9)

mwah 💋 sign-off: this one lives under ./drivers/virt/nitro_enclaves, and it’s dated October 2026. slay. 🎀