Kernel-bypass by design
Data lands directly in pre-registered host memory via RDMA Write. The receiving CPU is only notified once a full frame or buffer has arrived, not per packet.
The stream2roce IP core turns an AXI4-Stream into RoCEv2 RDMA writes entirely in FPGA logic, streaming data straight into remote host memory. It uses the same transport that GigE Vision 3.0 adopts for high-speed image streaming, works with any Ethernet MAC, and scales from 1 GbE up to 800 Gbit/s.
Vendor-independent. Efinix, Lattice, AMD/Xilinx, Altera and Microchip.
stream2roce takes one or more data streams and writes them directly into the memory of a remote host over standard Ethernet. The full RoCEv2 stack runs in hardware: transport headers, reliable-connection retransmission, ICRC and UDP, IP and Ethernet framing. There is no embedded network stack, no sensor-side driver and no CPU in the payload path.
Data lands directly in pre-registered host memory via RDMA Write. The receiving CPU is only notified once a full frame or buffer has arrived, not per packet.
Reliable-Connection and Unreliable-Connection modes, with per-QP sequence numbers, ACK and NAK handling and automatic retransmission with a run-time-tunable timeout.
The payload interface is a plain AXI4-Stream. Cameras, ADCs, LiDAR, radar or an on-chip processing chain: anything on a stream becomes an RDMA flow.
The essentials are below. The full interface specification, register map and integration guide come with an evaluation engagement.
Each queue pair owns its packetizer and a hardware retransmission buffer. A shared framer chain then merges all streams, adds UDP, IP and Ethernet, computes the RoCE ICRC and hands finished frames to any standard Ethernet MAC. A lightweight receive path parses incoming ACKs to close the reliability loop.
GigE Vision 3.0, released in 2025, adopts RoCEv2 and RDMA as its high-speed streaming transport next to classic GVSP. Image data is written straight into host memory at 10 to 400 Gbit/s, with no CPU copy. Because the standard defines its data channel directly on RoCEv2, this core can act as the transmit engine of a GigE Vision 3.0 device.
Some GPU vendors offer FPGA sensor bridges that stream RoCEv2 RDMA into GPU memory through their own network cards. stream2roce is an independent alternative for that transmit role. It runs on the FPGA you choose and delivers to a standard RoCEv2 host, with no tie to a single FPGA, network-card or GPU vendor.
| Aspect | P2L2 stream2roce | Proprietary GPU-vendor bridge |
|---|---|---|
| Role | FPGA-native RoCEv2 transmit engine | FPGA bridge tied to one vendor's host |
| Transport | ✓RoCEv2 RDMA Write, RC and UC, HW retransmission | ✓RoCEv2 RDMA write |
| Host CPU in data path | ✓None | ✓None |
| Receiving host | ✓Any standard RoCEv2 host | ×One vendor's card and GPU |
| GPU lock-in | ✓None | ×Single GPU ecosystem |
| Own and extend the IP | ✓Licensed and adaptable | ×Closed platform |
stream2roce targets any standard RoCEv2 receiver, so you keep full control over your FPGA, network-card and host choices.
Any application that moves high-rate sensor or streaming data into a host, while keeping the CPU free for processing, is a fit.
GigE Vision 3.0 cameras and frame-grabbers, with RDMA image delivery at 10 to 100 GbE.
Endoscopy, ultrasound and digital pathology, with low-latency ingest into GPU and AI hosts.
Autonomous and ADAS test rigs streaming multiple sensors over a single link.
High-rate ADC and instrumentation data captured straight into server memory.
Feed GPU inference pipelines from a vendor-neutral FPGA front end.
Move processed results from acceleration fabric into host RAM without a CPU copy.
Multi-stream RoCEv2 transmit core with hardware retransmission and ICRC. Runs at 1 GbE over GMII or RGMII without a transceiver, and at 10 GbE. Hardware-proven against a standard Linux RDMA host and verified with UVVM and VUnit.
25, 50 and 100 Gbit/s, and up to 400 and 800 Gbit/s. Ported to Efinix, Lattice, AMD/Xilinx, Altera or Microchip.
GigE Vision 3.0 and GVSP transmit layer, connection management and metadata handshake, host driver support.
Tell us your sensor interface, target FPGA and line rate. We will scope a stream2roce configuration and share the detailed interface specification and evaluation terms.