From: Jakub Kicinski <kuba@kernel.org>
To: Vishwanath Seshagiri <vishs@meta.com>
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>, "David Wei" <dw@davidwei.uk>,
"Matteo Croce" <technoboy85@gmail.com>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
netdev@vger.kernel.org, virtualization@lists.linux.dev,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH net-next v4 2/2] selftests: virtio_net: add buffer circulation test
Date: Wed, 4 Feb 2026 21:25:11 -0800 [thread overview]
Message-ID: <20260204212511.017153cd@kernel.org> (raw)
In-Reply-To: <20260204193617.1200752-3-vishs@meta.com>
On Wed, 4 Feb 2026 11:36:17 -0800 Vishwanath Seshagiri wrote:
> Add iperf3-based test to verify RX buffer handling under load.
> Optionally logs page_pool tracepoints when available.
TBH I wouldn't bother with this.
We run full battery of driver tests in netdev CI, there's not much
value in a dedicated virtio test that just runs iperf...
--
pw-bot: cr
next prev parent reply other threads:[~2026-02-05 5:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 19:36 [PATCH net-next v4 0/2] virtio_net: add page_pool support Vishwanath Seshagiri
2026-02-04 19:36 ` [PATCH net-next v4 1/2] virtio_net: add page_pool support for buffer allocation Vishwanath Seshagiri
2026-02-05 3:54 ` Jason Wang
2026-02-05 5:30 ` Michael S. Tsirkin
2026-02-05 6:34 ` Vishwanath Seshagiri
2026-02-05 6:40 ` Michael S. Tsirkin
2026-02-05 18:48 ` Vishwanath Seshagiri
2026-02-04 19:36 ` [PATCH net-next v4 2/2] selftests: virtio_net: add buffer circulation test Vishwanath Seshagiri
2026-02-05 4:12 ` Jason Wang
2026-02-05 5:13 ` Vishwanath Seshagiri
2026-02-05 5:25 ` Jakub Kicinski [this message]
2026-02-05 6:24 ` Vishwanath Seshagiri
2026-02-05 6:24 ` Michael S. Tsirkin
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=20260204212511.017153cd@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jasowang@redhat.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=technoboy85@gmail.com \
--cc=virtualization@lists.linux.dev \
--cc=vishs@meta.com \
--cc=xuanzhuo@linux.alibaba.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.