Re: Designing a safe RX-zero-copy Memory Model for Networking

On 13.12.2016 17:10, Jesper Dangaard Brouer wrote:

quoted

What is bad about RDMA is that it is a separate kernel subsystem.
What I would like to see is a deeper integration with the network
stack so that memory regions can be registred with a network socket
and work requests then can be submitted and processed that directly
read and write in these regions. The network stack should provide the
services that the hardware of the NIC does not suppport as usual.

Interesting.  So you even imagine sockets registering memory regions
with the NIC.  If we had a proper NIC HW filter API across the drivers,
to register the steering rule (like ibv_create_flow), this would be
doable, but we don't (DPDK actually have an interesting proposal[1])

On a side note, this is what windows does with RIO ("registered I/O").
Maybe you want to look at the API to get some ideas: allocating and
pinning down memory in user space and registering that with sockets to
get zero-copy IO.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>