From: Jakub Kicinski <kuba@kernel.org>
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
Michael Chan <michael.chan@broadcom.com>,
Pavan Chebbi <pavan.chebbi@broadcom.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Joshua Washington <joshwash@google.com>,
Harshitha Ramamurthy <hramamurthy@google.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Alexander Duyck <alexanderduyck@fb.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Shuah Khan <shuah@kernel.org>,
Willem de Bruijn <willemb@google.com>,
Ankit Garg <nktgrg@google.com>,
Tim Hostetler <thostet@google.com>,
Alok Tiwari <alok.a.tiwari@oracle.com>,
Ziwei Xiao <ziweixiao@google.com>,
John Fraker <jfraker@google.com>,
Praveen Kaligineedi <pkaligineedi@google.com>,
Mohsin Bashir <mohsin.bashr@gmail.com>, Joe Damato <joe@dama.to>,
Mina Almasry <almasrymina@google.com>,
Dimitri Daskalakis <dimitri.daskalakis1@gmail.com>,
Stanislav Fomichev <sdf@fomichev.me>,
Kuniyuki Iwashima <kuniyu@google.com>,
Samiullah Khawaja <skhawaja@google.com>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
David Wei <dw@davidwei.uk>, Yue Haibing <yuehaibing@huawei.com>,
Haiyue Wang <haiyuewa@163.com>, Jens Axboe <axboe@kernel.dk>,
Simon Horman <horms@kernel.org>,
Vishwanath Seshagiri <vishs@fb.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kselftest@vger.kernel.org, dtatulea@nvidia.com,
kernel-team@meta.com, io-uring@vger.kernel.org
Subject: Re: [PATCH net-next v9 0/9] Add support for providers with large rx buffer
Date: Mon, 19 Jan 2026 08:57:37 -0800 [thread overview]
Message-ID: <20260119085737.2161f9e6@kernel.org> (raw)
In-Reply-To: <7ab5309d-8654-4fa8-9a1e-24b948bccba2@gmail.com>
On Mon, 19 Jan 2026 13:54:37 +0000 Pavel Begunkov wrote:
> On 1/15/26 17:11, Pavel Begunkov wrote:
> > Note: it's net/ only bits and doesn't include changes, which shoulf be
> > merged separately and are posted separately. The full branch for
> > convenience is at [1], and the patch is here:
>
> Looks like patchwork says the patches don't apply, but the branch
> still merges well. Alternatively, I can rebase on top of net-next
> and likely delay the final io_uring commit to one release after.
Yes, David refactored the test in the meantime :/
I'll pull the branch.
prev parent reply other threads:[~2026-01-19 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 17:11 [PATCH net-next v9 0/9] Add support for providers with large rx buffer Pavel Begunkov
2026-01-15 17:11 ` [PATCH net-next v9 1/9] net: memzero mp params when closing a queue Pavel Begunkov
2026-01-21 2:20 ` patchwork-bot+netdevbpf
2026-01-15 17:11 ` [PATCH net-next v9 2/9] net: reduce indent of struct netdev_queue_mgmt_ops members Pavel Begunkov
2026-01-15 17:11 ` [PATCH net-next v9 3/9] net: add bare bone queue configs Pavel Begunkov
2026-01-15 17:11 ` [PATCH net-next v9 4/9] net: pass queue rx page size from memory provider Pavel Begunkov
2026-01-15 17:11 ` [PATCH net-next v9 5/9] eth: bnxt: store rx buffer size per queue Pavel Begunkov
2026-01-15 17:11 ` [PATCH net-next v9 6/9] eth: bnxt: adjust the fill level of agg queues with larger buffers Pavel Begunkov
2026-01-15 17:12 ` [PATCH net-next v9 7/9] eth: bnxt: support qcfg provided rx page size Pavel Begunkov
2026-01-15 17:12 ` [PATCH net-next v9 8/9] selftests: iou-zcrx: test large chunk sizes Pavel Begunkov
2026-01-15 17:12 ` [PATCH net-next v9 9/9] io_uring/zcrx: document area chunking parameter Pavel Begunkov
2026-01-19 13:54 ` [PATCH net-next v9 0/9] Add support for providers with large rx buffer Pavel Begunkov
2026-01-19 16:57 ` Jakub Kicinski [this message]
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=20260119085737.2161f9e6@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=alexanderduyck@fb.com \
--cc=almasrymina@google.com \
--cc=alok.a.tiwari@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=asml.silence@gmail.com \
--cc=ast@kernel.org \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dimitri.daskalakis1@gmail.com \
--cc=dtatulea@nvidia.com \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=haiyuewa@163.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=ilias.apalodimas@linaro.org \
--cc=io-uring@vger.kernel.org \
--cc=jfraker@google.com \
--cc=joe@dama.to \
--cc=john.fastabend@gmail.com \
--cc=joshwash@google.com \
--cc=kernel-team@meta.com \
--cc=kuniyu@google.com \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=michael.chan@broadcom.com \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nktgrg@google.com \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=pkaligineedi@google.com \
--cc=saeedm@nvidia.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=skhawaja@google.com \
--cc=tariqt@nvidia.com \
--cc=thostet@google.com \
--cc=vishs@fb.com \
--cc=willemb@google.com \
--cc=yuehaibing@huawei.com \
--cc=ziweixiao@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.