[RFC PATCH v3 12/12] selftests: add ncdevmem, netcat for devmem TCP
Jakub Kicinski
kuba at kernel.org
Mon Nov 13 22:20:20 UTC 2023
On Sun, 12 Nov 2023 20:08:10 -0800 Mina Almasry wrote:
> 1. For (b), would it be OK to implement a very minimal version of
> queue_[stop|start]/queue_mem_[alloc|free], which I use for the sole
> purpose of reposting buffers to an individual queue, and then later
> whoever picks up your queue API effort (maybe me) extends the
> implementation to do the rest of the things you described in your
> email? If not, what is the minimal queue API I can implement and use
> for devmem TCP?
Any form of queue API is better than a temporary ndo.
IIUC it will not bubble up into uAPI in any way so we can extend/change
it later as needed.
> 2. Since this is adding ndo, do I need to implement the ndo for 2
> drivers or is GVE sufficient?
One driver is fine, especially if we're doing this instead of the reset
hack.
More information about the dri-devel
mailing list