From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
netdev@vger.kernel.org, Jason Wang <jasowang@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] virtio_net: Enforce minimum TX ring size for reliability
Date: Wed, 21 May 2025 17:34:07 +0800 [thread overview]
Message-ID: <1747820047.4914944-3-xuanzhuo@linux.alibaba.com> (raw)
In-Reply-To: <20250521092236.661410-4-lvivier@redhat.com>
On Wed, 21 May 2025 11:22:36 +0200, Laurent Vivier <lvivier@redhat.com> wrote:
> The `tx_may_stop()` logic stops TX queues if free descriptors
> (`sq->vq->num_free`) fall below the threshold of (`MAX_SKB_FRAGS` + 2).
> If the total ring size (`ring_num`) is not strictly greater than this
> value, queues can become persistently stopped or stop after minimal
> use, severely degrading performance.
>
> A single sk_buff transmission typically requires descriptors for:
> - The virtio_net_hdr (1 descriptor)
> - The sk_buff's linear data (head) (1 descriptor)
> - Paged fragments (up to MAX_SKB_FRAGS descriptors)
>
> This patch enforces that the TX ring size ('ring_num') must be strictly
> greater than (MAX_SKB_FRAGS + 2). This ensures that the ring is
> always large enough to hold at least one maximally-fragmented packet
> plus at least one additional slot.
>
> Reported-by: Lei Yang <leiyang@redhat.com>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
Reviewed-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> ---
> drivers/net/virtio_net.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> index ff4160243538..50b851834ae2 100644
> --- a/drivers/net/virtio_net.c
> +++ b/drivers/net/virtio_net.c
> @@ -3481,6 +3481,12 @@ static int virtnet_tx_resize(struct virtnet_info *vi, struct send_queue *sq,
> {
> int qindex, err;
>
> + if (ring_num <= MAX_SKB_FRAGS + 2) {
> + netdev_err(vi->dev, "tx size (%d) cannot be smaller than %d\n",
> + ring_num, MAX_SKB_FRAGS + 2);
> + return -EINVAL;
> + }
> +
> qindex = sq - vi->sq;
>
> virtnet_tx_pause(vi, sq);
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-05-21 9:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 9:22 [PATCH v2 0/3] virtio: Fixes for TX ring sizing and resize error reporting Laurent Vivier
2025-05-21 9:22 ` [PATCH v2 1/3] virtio_ring: Fix error reporting in virtqueue_resize Laurent Vivier
2025-05-22 1:56 ` Jason Wang
2025-05-21 9:22 ` [PATCH v2 2/3] virtio_net: Cleanup '2+MAX_SKB_FRAGS' Laurent Vivier
2025-05-21 9:33 ` Xuan Zhuo
2025-05-22 1:56 ` Jason Wang
2025-05-21 9:22 ` [PATCH v2 3/3] virtio_net: Enforce minimum TX ring size for reliability Laurent Vivier
2025-05-21 9:34 ` Xuan Zhuo [this message]
2025-05-22 1:56 ` Jason Wang
2025-05-27 7:32 ` [PATCH v2 0/3] virtio: Fixes for TX ring sizing and resize error reporting Lei Yang
2025-05-28 6:24 ` Paolo Abeni
2025-05-28 7:20 ` Michael S. Tsirkin
2025-06-16 13:07 ` Laurent Vivier
2025-06-23 8:23 ` Laurent Vivier
2025-07-03 7:43 ` Laurent Vivier
2025-07-03 9:30 ` Michael S. Tsirkin
2025-07-03 9:31 ` Michael S. Tsirkin
2025-07-03 9:34 ` Paolo Abeni
2025-07-08 0:29 ` Jakub Kicinski
2025-07-08 16:03 ` Simon Horman
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=1747820047.4914944-3-xuanzhuo@linux.alibaba.com \
--to=xuanzhuo@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
/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®