How does RDMA bypass kernel overhead in Exadata?
In a traditional networking stack, sending data from a database to storage is like a package going through five different post offices before it reaches its destination. Each "post office" (the OS kernel, context switches, interrupts) adds a tiny delay.
RDMA (Remote Direct Memory Access) over the 100Gbps RoCE (RDMA over Converged Ethernet) fabric is the "express lane" that allows Exadata to bypass the kernel entirely. Here is how it works.
In a non-Exadata system, when the database wants to write data to storage, the request must travel through the Operating System Kernel:
Context Switching: The CPU must switch from "User Mode" (Database) to "Kernel Mode" (OS).
Data Copying: The data is copied from the Database buffer to the OS Network buffer.
Interrupts: The CPU on the receiving storage server must stop what it’s doing to handle the incoming network packet.
This process consumes CPU cycles and adds hundreds of microseconds of latency.
RDMA allows a Database Server to read or write directly into the memory of a Storage Cell. The "Magic" happens because the Network Interface Card (NIC) handles the entire transfer in hardware.
Memory Registration: At startup, the Exadata Storage Software "registers" specific parts of its RAM (and PMEM) with the RoCE NIC.
Zero-Copy: When the database needs to write a Redo Log or read a block, it tells the NIC the memory address on the remote storage cell. The data moves directly from DB RAM to Storage RAM.
Kernel Bypass: The OS Kernel is never told that the transfer is happening. The CPU is not interrupted.
Hardware Offload: The NIC hardware manages the packet routing, error checking, and acknowledgment.
Oracle utilizes a specialized protocol called RDS (Reliable Datagram Sockets) over RoCE. This protocol is "Database-Aware."
Because the database doesn't have to wait for the OS to schedule a network task, the time it takes to send a message drops from ~50 microseconds down to less than 5 microseconds.
Bypassing the kernel provides three massive technical advantages:
Ultra-Low Latency: By removing the "OS middleman," Exadata achieves sub-19 microsecond latencies for persistent memory writes.
Lower CPU Utilization: Since the NIC handles the data transfer, the Database and Storage CPUs are free to do what they do best: run SQL and process data.
Higher Throughput: Without the overhead of memory copying and context switching, the 100Gbps fabric can be saturated much more efficiently.
| Feature | Traditional Networking (TCP/IP) | Exadata RDMA (RoCE) |
| CPU Involvement | High (Context switches/Interrupts). | Near Zero (Offloaded to NIC). |
| Data Copies | Multiple (User space to Kernel space). | Zero (Direct Memory-to-Memory). |
| Latency | 100+ Microseconds. | < 19 Microseconds. |
| OS Role | Manages every packet. | Bypassed during data transfer. |
RDMA is the reason Exadata can scale to millions of IOPS. By turning the network into a simple "extension of memory," it removes the software bottlenecks that prevent traditional servers from ever reaching the full potential of modern NVMe and PMEM hardware.