From: "Michael S. Tsirkin" <mst@redhat.com>
To: Wenliang Wang <wangwenliang.1995@bytedance.com>
Cc: jasowang@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] virtio_net: suppress cpu stall when free_unused_bufs
Date: Thu, 27 Apr 2023 21:09:20 -0400 [thread overview]
Message-ID: <20230427210851-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230427104618.3297348-1-wangwenliang.1995@bytedance.com>
On Thu, Apr 27, 2023 at 06:46:18PM +0800, Wenliang Wang wrote:
> For multi-queue and large ring-size use case, the following error
> occurred when free_unused_bufs:
> rcu: INFO: rcu_sched self-detected stall on CPU.
>
> Signed-off-by: Wenliang Wang <wangwenliang.1995@bytedance.com>
pls send vN+1 as a new thread not as a reply in existing thread of vN.
> ---
> v2:
> -add need_resched check.
> -apply same logic to sq.
> ---
> drivers/net/virtio_net.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> index ea1bd4bb326d..573558b69a60 100644
> --- a/drivers/net/virtio_net.c
> +++ b/drivers/net/virtio_net.c
> @@ -3559,12 +3559,16 @@ static void free_unused_bufs(struct virtnet_info *vi)
> struct virtqueue *vq = vi->sq[i].vq;
> while ((buf = virtqueue_detach_unused_buf(vq)) != NULL)
> virtnet_sq_free_unused_buf(vq, buf);
> + if (need_resched())
> + schedule();
> }
>
> for (i = 0; i < vi->max_queue_pairs; i++) {
> struct virtqueue *vq = vi->rq[i].vq;
> while ((buf = virtqueue_detach_unused_buf(vq)) != NULL)
> virtnet_rq_free_unused_buf(vq, buf);
> + if (need_resched())
> + schedule();
> }
> }
>
> --
> 2.20.1
next prev parent reply other threads:[~2023-04-28 1:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 4:34 [PATCH] virtio_net: suppress cpu stall when free_unused_bufs Wenliang Wang
2023-04-27 6:20 ` Xuan Zhuo
2023-04-27 7:02 ` Wenliang Wang
2023-04-27 7:13 ` Xuan Zhuo
2023-04-27 8:12 ` Michael S. Tsirkin
2023-04-27 8:13 ` Xuan Zhuo
2023-04-27 8:23 ` Michael S. Tsirkin
2023-04-27 8:49 ` Wenliang Wang
2023-04-27 8:51 ` Xuan Zhuo
2023-04-27 10:46 ` [PATCH v2] " Wenliang Wang
2023-04-28 1:09 ` Michael S. Tsirkin [this message]
2023-04-27 10:45 ` [PATCH] " Qi Zheng
2023-04-28 13:56 ` Willem de Bruijn
-- strict thread matches above, loose matches on Subject: below --
2023-04-28 2:26 [PATCH v2] " Wenliang 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=20230427210851-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wangwenliang.1995@bytedance.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;
as well as URLs for NNTP newsgroup(s).