All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Bobby Eshleman <bobbyeshleman@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	Willem de Bruijn <willemb@google.com>,
	Neal Cardwell <ncardwell@google.com>,
	David Ahern <dsahern@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Jonathan Corbet <corbet@lwn.net>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	Shuah Khan <shuah@kernel.org>,
	Donald Hunter <donald.hunter@gmail.com>,
	Mina Almasry <almasrymina@google.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kselftest@vger.kernel.org,
	Stanislav Fomichev <sdf@fomichev.me>,
	asml.silence@gmail.com, matttbe@kernel.org, skhawaja@google.com,
	Bobby Eshleman <bobbyeshleman@meta.com>
Subject: Re: [PATCH net-next v8 0/5] net: devmem: improve cpu cost of RX token management
Date: Thu, 8 Jan 2026 06:42:00 -0800	[thread overview]
Message-ID: <20260108064200.7faf9735@kernel.org> (raw)
In-Reply-To: <aV80jCHD9PGaOr87@devvm11784.nha0.facebook.com>

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:
> > On Wed, 07 Jan 2026 16:57:34 -0800 Bobby Eshleman wrote:  
> > > 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

  reply	other threads:[~2026-01-08 14:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08  0:57 [PATCH net-next v8 0/5] net: devmem: improve cpu cost of RX token management Bobby Eshleman
2026-01-08  0:57 ` [PATCH net-next v8 1/5] net: devmem: rename tx_vec to vec in dmabuf binding Bobby Eshleman
2026-01-08  0:57 ` [PATCH net-next v8 2/5] net: devmem: refactor sock_devmem_dontneed for autorelease split Bobby Eshleman
2026-01-08  0:57 ` [PATCH net-next v8 3/5] net: devmem: implement autorelease token management Bobby Eshleman
2026-01-08 19:19   ` kernel test robot
2026-01-08 20:21   ` kernel test robot
2026-01-08  0:57 ` [PATCH net-next v8 4/5] net: devmem: document NETDEV_A_DMABUF_AUTORELEASE netlink attribute Bobby Eshleman
2026-01-08  0:57 ` [PATCH net-next v8 5/5] selftests: drv-net: devmem: add autorelease test Bobby Eshleman
2026-01-08  3:30 ` [PATCH net-next v8 0/5] net: devmem: improve cpu cost of RX token management Jakub Kicinski
2026-01-08  4:37   ` Bobby Eshleman
2026-01-08 14:42     ` Jakub Kicinski [this message]
2026-01-08 17:06       ` Bobby Eshleman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260108064200.7faf9735@kernel.org \
    --to=kuba@kernel.org \
    --cc=almasrymina@google.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=asml.silence@gmail.com \
    --cc=bobbyeshleman@gmail.com \
    --cc=bobbyeshleman@meta.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=matttbe@kernel.org \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=skhawaja@google.com \
    --cc=willemb@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.