Thread (41 messages) flat view 41 messages, 3 authors, 2024-08-13

Re: [PATCH net-next v18 07/14] memory-provider: dmabuf devmem memory provider

From: Jakub Kicinski <kuba@kernel.org>
Date: 2024-08-13 14:39:20
Also in: bpf, dri-devel, linux-alpha, linux-arch, linux-kselftest, linux-media, linux-mips, linux-trace-kernel, lkml, netdev, sparclinux

On Tue, 13 Aug 2024 03:31:13 +0100 Pavel Begunkov wrote:
I'm getting lost, so repeating myself a bit. What I think
would be a good approach is if we get an error back from
the driver if it doesn't support netiov / providers.

netdev_rx_queue_restart() {
	...
	err = dev->queue_mgmt_ops->ndo_queue_mem_alloc();
	if (err == -EOPNOTSUPP) // the driver doesn't support netiov
		return -EOPNOTSUPP;
	...
}

That can be done if drivers opt in to support providers,
e.g. via a page pool flag.

What I think wouldn't be a great option is getting back a
"success" from the driver even though it ignored
page pool params are not the right place for a supported flag.
Sooner or later we'll want to expose this flag to user space.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help