Thread (12 messages) 12 messages, 3 authors, 2026-01-08

Re: [PATCH net-next v8 0/5] net: devmem: improve cpu cost of RX token management

From: Jakub Kicinski <kuba@kernel.org>
Date: 2026-01-08 14:42:02
Also in: linux-arch, linux-doc, linux-kselftest, lkml

On Wed, 7 Jan 2026 20:37:32 -0800 Bobby Eshleman wrote:
On Wed, Jan 07, 2026 at 07:30:13PM -0800, Jakub Kicinski wrote:
quoted
On Wed, 07 Jan 2026 16:57:34 -0800 Bobby Eshleman wrote:  
quoted
This series improves the CPU cost of RX token management by adding an
attribute to NETDEV_CMD_BIND_RX that configures sockets using the
binding to avoid the xarray allocator and instead use a per-binding niov
array and a uref field in niov.  
net/ipv4/tcp.c:2600:41: error: implicit declaration of function ‘net_devmem_dmabuf_binding_get’; did you mean ‘net_devmem_dmabuf_binding_put’? [-Wimplicit-function-declaration]
 2600 |                                         net_devmem_dmabuf_binding_get(binding);
      |                                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                                         net_devmem_dmabuf_binding_put
I see that net_devmem_dmabuf_binding_get() is lacking a
stub for CONFIG_NET_DEVMEM=n ...

Just curious how pw works... is this a randconfig catch? I ask because
all of the build targets pass for this series (build_allmodconfig_warn,
build_clang, etc.. locally and on patchwork.kernel.org), and if there is
a config that pw uses that I'm missing in my local checks I'd like to
add it.
kunit hit it on our end
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help