NE_RECV_DATA_SIZE(9)

💖 NAME 💖

okay so this is the NE_RECV_DATA_SIZE(9) page, from the Kernel API Manual — and it is literally the size of the receive buffer, in bytes. that’s the whole assignment, bestie. no cap. 💅

✨ SYNOPSIS ✨

NE_RECV_DATA_SIZE

just the symbol, standing there looking iconic. 🫶

🌈 SEE ALSO 🌈

first up, the kernel file is ./drivers/virt/nitro_enclaves/ne_pci_dev.h — go look at it, it’s giving source-of-truth realness. then the whole crew, in the original order:

• 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_SEND_DATA(9)
• NE_RECV_DATA(9)
• Device MMIO buffer sizes(9)
• NE_SEND_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)

okay that’s the whole page, bestie — source/version: ./drivers/virt/nitro_enclaves, date: October 2026, page: NE_RECV_DATA_SIZE(9). slay 💅✨