From: Vishwanath Seshagiri <vishs@meta.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "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>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>, "David Wei" <dw@davidwei.uk>,
netdev@vger.kernel.org, virtualization@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 2/2] selftests: virtio_net: add buffer circulation test
Date: Thu, 29 Jan 2026 13:33:42 -0800 [thread overview]
Message-ID: <21c8046f-cc80-4063-b6f3-f8a1e9f8d5c2@meta.com> (raw)
In-Reply-To: <20260128171144-mutt-send-email-mst@kernel.org>
On 1/28/26 2:12 PM, Michael S. Tsirkin wrote:
> On Wed, Jan 28, 2026 at 01:20:31PM -0800, Vishwanath Seshagiri wrote:
>> Add iperf3-based test to verify RX buffer handling under load.
>> Optionally logs page_pool tracepoints when available.
>>
>> Signed-off-by: Vishwanath Seshagiri <vishs@meta.com>
>> ---
>> .../drivers/net/virtio_net/basic_features.sh | 70 +++++++++++++++++++
>> 1 file changed, 70 insertions(+)
>>
>> diff --git a/tools/testing/selftests/drivers/net/virtio_net/basic_features.sh b/tools/testing/selftests/drivers/net/virtio_net/basic_features.sh
>> index cf8cf816ed48..c2c8023d2b92 100755
>> --- a/tools/testing/selftests/drivers/net/virtio_net/basic_features.sh
>> +++ b/tools/testing/selftests/drivers/net/virtio_net/basic_features.sh
>> @@ -6,6 +6,7 @@
>> ALL_TESTS="
>> initial_ping_test
>> f_mac_test
>> + buffer_circulation_test
>> "
>>
>> source virtio_net_common.sh
>> @@ -16,6 +17,8 @@ source "$lib_dir"/../../../net/forwarding/lib.sh
>> h1=${NETIFS[p1]}
>> h2=${NETIFS[p2]}
>>
>> +require_command iperf3
>> +
>> h1_create()
>> {
>> simple_if_init $h1 $H1_IPV4/24 $H1_IPV6/64
>> @@ -83,6 +86,73 @@ f_mac_test()
>> log_test "$test_name"
>> }
>>
>> +buffer_circulation_test()
>> +{
>> + RET=0
>> + local test_name="buffer circulation"
>> + local tracefs="/sys/kernel/tracing"
>> +
>> + setup_cleanup
>> + setup_prepare
>> +
>> + ping -c 1 -I $h1 $H2_IPV4 >/dev/null
>> + if [ $? -ne 0 ]; then
>> + check_err 1 "Ping failed"
>> + log_test "$test_name"
>> + return
>> + fi
>> +
>> + local rx_start=$(cat /sys/class/net/$h2/statistics/rx_packets)
>> + local tx_start=$(cat /sys/class/net/$h1/statistics/tx_packets)
>> +
>> + if [ -d "$tracefs/events/page_pool" ]; then
>> + echo > "$tracefs/trace"
>> + echo 1 > "$tracefs/events/page_pool/enable"
>> + fi
>> +
>> + iperf3 -s --bind-dev $h2 -p 5201 &>/dev/null &
>> + local server_pid=$!
>> + sleep 1
>> +
>> + if ! kill -0 $server_pid 2>/dev/null; then
>> + if [ -d "$tracefs/events/page_pool" ]; then
>> + echo 0 > "$tracefs/events/page_pool/enable"
>> + fi
>> + check_err 1 "iperf3 server died"
>> + log_test "$test_name"
>> + return
>> + fi
>> +
>> + iperf3 -c $H2_IPV4 --bind-dev $h1 -p 5201 -t 5 >/dev/null 2>&1
>
> is using hard coded ports like this fine?
> running several in parallel will fail ...
I will use a random port in the ephemeral range to avoid
conflicts when running tests in parallel. Will fix it in v3.
>
>
>> + local iperf_ret=$?
>> +
>> + kill $server_pid 2>/dev/null || true
>> + wait $server_pid 2>/dev/null || true
>> +
>> + if [ -d "$tracefs/events/page_pool" ]; then
>> + echo 0 > "$tracefs/events/page_pool/enable"
>> + local trace="$tracefs/trace"
>> + local hold=$(grep -c "page_pool_state_hold" "$trace" 2>/dev/null)
>> + local release=$(grep -c "page_pool_state_release" "$trace" 2>/dev/null)
>> + log_info "page_pool events: hold=${hold:-0}, release=${release:-0}"
>> + fi
>> +
>> + local rx_end=$(cat /sys/class/net/$h2/statistics/rx_packets)
>> + local tx_end=$(cat /sys/class/net/$h1/statistics/tx_packets)
>> + local rx_delta=$((rx_end - rx_start))
>> + local tx_delta=$((tx_end - tx_start))
>> +
>> + log_info "Circulated TX:$tx_delta RX:$rx_delta"
>> +
>> + if [ $iperf_ret -ne 0 ]; then
>> + check_err 1 "iperf3 failed"
>> + elif [ "$rx_delta" -lt 10000 ]; then
>> + check_err 1 "Too few packets: $rx_delta"
>> + fi
>> +
>> + log_test "$test_name"
>> +}
>> +
>> setup_prepare()
>> {
>> virtio_device_rebind $h1
>> --
>> 2.47.3
>
next prev parent reply other threads:[~2026-01-29 21:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 21:20 [PATCH v2 net-next 0/2] virtio_net: add page_pool support Vishwanath Seshagiri
2026-01-28 21:20 ` [PATCH v2 net-next 1/2] virtio_net: add page_pool support for buffer allocation Vishwanath Seshagiri
2026-01-29 2:54 ` Jason Wang
2026-01-29 17:20 ` Vishwanath Seshagiri
2026-01-29 6:30 ` Michael S. Tsirkin
2026-01-29 17:48 ` Vishwanath Seshagiri
2026-01-28 21:20 ` [PATCH v2 net-next 2/2] selftests: virtio_net: add buffer circulation test Vishwanath Seshagiri
2026-01-28 22:12 ` Michael S. Tsirkin
2026-01-29 21:33 ` Vishwanath Seshagiri [this message]
2026-01-29 1:37 ` [PATCH v2 net-next 0/2] virtio_net: add page_pool support Jakub Kicinski
2026-01-29 5:45 ` Vishwanath Seshagiri
2026-01-29 2:55 ` Jason Wang
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=21c8046f-cc80-4063-b6f3-f8a1e9f8d5c2@meta.com \
--to=vishs@meta.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®