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 0/2] virtio_net: add page_pool support
Date: Wed, 7 Jan 2026 21:23:46 -0800 [thread overview]
Message-ID: <ecda097e-e3cc-47c4-aad3-61f6af950a71@meta.com> (raw)
In-Reply-To: <20260107032738-mutt-send-email-mst@kernel.org>
On 1/7/26 12:28 AM, Michael S. Tsirkin wrote:
> On Tue, Jan 06, 2026 at 02:19:22PM -0800, Vishwanath Seshagiri wrote:
>> Introduce page_pool support in virtio_net driver in order to recycle
>> pages in RX buffer allocation and avoid reallocating through the page
>> allocator. This applies to mergeable and small buffer modes.
>>
>> The patch has been tested using the included selftests and additional
>> edge case scripts covering device unbind/bind cycles, rapid interface
>> open/close, traffic during close, ethtool stress with feature toggling,
>> close with pending refill work, and data integrity verification.
>
>
> Yay! thanks for working on this!
> Could you share perf data please?
> After all, page pool is an optimization.
Thanks! I'll add benchmark numbers in v2 of the patch.
Beyond performance, page pool support is pre requisite for enabling
memory provider based zero copy implementations in virtio_net such as
devmem TCP and io-uring ZCRX. These features require the driver to use
page pools for buffer management. I'll update the cover letter to make
this motivation clearer.
>
>
>> Vishwanath Seshagiri (2):
>> virtio_net: add page pool support for buffer allocation
>> selftests: virtio_net: add buffer circulation test
>>
>> drivers/net/virtio_net.c | 246 +++++++++++++++---
>> .../drivers/net/virtio_net/basic_features.sh | 70 +++++
>> 2 files changed, 275 insertions(+), 41 deletions(-)
>>
>> --
>> 2.47.3
>
next prev parent reply other threads:[~2026-01-08 5:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 22:19 [PATCH 0/2] virtio_net: add page_pool support Vishwanath Seshagiri
2026-01-06 22:19 ` [PATCH 1/2] virtio_net: add page pool support for buffer allocation Vishwanath Seshagiri
2026-01-07 3:49 ` Xuan Zhuo
2026-01-07 18:41 ` Vishwanath Seshagiri
2026-01-08 3:16 ` Jason Wang
2026-01-08 6:23 ` Vishwanath Seshagiri
2026-01-09 3:16 ` Jason Wang
2026-01-09 6:50 ` Michael S. Tsirkin
2026-01-09 20:36 ` Vishwanath Seshagiri
2026-01-10 1:57 ` Vishwanath Seshagiri
2026-01-12 3:15 ` Jason Wang
2026-01-06 22:19 ` [PATCH 2/2] selftests: virtio_net: add buffer circulation test Vishwanath Seshagiri
2026-01-07 8:28 ` [PATCH 0/2] virtio_net: add page_pool support Michael S. Tsirkin
2026-01-08 5:23 ` Vishwanath Seshagiri [this message]
2026-01-28 20:19 ` Michael S. Tsirkin
2026-01-28 20:27 ` Vishwanath Seshagiri
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=ecda097e-e3cc-47c4-aad3-61f6af950a71@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