Trapeze Messaging in a Nutshell
1. API and NIC preserve separation of header and payload.
Short, fixed-size control messages with optional attached payloads.
2. Unified buffering between file/VM/network subsystems.
Trapeze driver and integrated kernel RPC layer allocate buffers from system page frame pool.
Zero-copy payloads: map pages onto the NIC DMA rings and “inject” incoming payload frames into the page cache.
3. Large MTUs with scatter/gather.
4. NIC features for adaptive message pipelining, payload caching, payload demultiplexing, and interrupt suppression.