[net-next v1 00/16] Device Memory TCP
Shakeel Butt
shakeelb at google.com
Sun Dec 10 03:48:07 UTC 2023
On Thu, Dec 07, 2023 at 04:52:31PM -0800, Mina Almasry wrote:
[...]
>
> Today, the majority of the Device-to-Device data transfers the network are
'the network' in above can be removed.
> implemented as the following low level operations: Device-to-Host copy,
> Host-to-Host network transfer, and Host-to-Device copy.
>
[...]
>
> ** Part 5: recvmsg() APIs
>
> We define user APIs for the user to send and receive device memory.
>
> Not included with this RFC is the GVE devmem TCP support, just to
no more RFC
> simplify the review. Code available here if desired:
> https://github.com/mina/linux/tree/tcpdevmem
>
> This RFC is built on top of net-next with Jakub's pp-providers changes
no more RFC
[...]
>
> ** Test Setup
>
> Kernel: net-next with this RFC and memory provider API cherry-picked
no more RFC
> locally.
>
> Hardware: Google Cloud A3 VMs.
>
> NIC: GVE with header split & RSS & flow steering support.
>
More information about the dri-devel
mailing list