From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Wenliang Wang <wangwenliang.1995@bytedance.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, zhengqi.arch@bytedance.com,
willemdebruijn.kernel@gmail.com,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
xuanzhuo@linux.alibaba.com
Subject: Re: [PATCH v4] virtio_net: suppress cpu stall when free_unused_bufs
Date: Sun, 7 May 2023 09:34:05 -0400 [thread overview]
Message-ID: <20230507093328-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACGkMEs_4kUzc6iSBWvhZA1+U70Pp0o+WhE0aQnC-5pECW7QXA@mail.gmail.com>
On Fri, May 05, 2023 at 11:28:25AM +0800, Jason Wang wrote:
> On Thu, May 4, 2023 at 10:27 AM Wenliang Wang
> <wangwenliang.1995@bytedance.com> 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.
> >
> > Fixes: 986a4f4d452d ("virtio_net: multiqueue support")
> > Signed-off-by: Wenliang Wang <wangwenliang.1995@bytedance.com>
> > ---
> > v2:
> > -add need_resched check.
> > -apply same logic to sq.
> > v3:
> > -use cond_resched instead.
> > v4:
> > -add fixes tag
> > ---
> > drivers/net/virtio_net.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> > index 8d8038538fc4..a12ae26db0e2 100644
> > --- a/drivers/net/virtio_net.c
> > +++ b/drivers/net/virtio_net.c
> > @@ -3560,12 +3560,14 @@ 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);
> > + cond_resched();
>
> Does this really address the case when the virtqueue is very large?
>
> Thanks
it does in that a very large queue is still just 64k in size.
we might however have 64k of these queues.
> > }
> >
> > 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);
> > + cond_resched();
> > }
> > }
> >
> > --
> > 2.20.1
> >
next prev parent reply other threads:[~2023-05-07 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 2:27 [PATCH v4] virtio_net: suppress cpu stall when free_unused_bufs Wenliang Wang
2023-05-04 7:06 ` Michael S. Tsirkin
2023-05-05 3:28 ` Jason Wang
2023-05-06 2:04 ` Xuan Zhuo
2023-05-07 13:34 ` Michael S. Tsirkin [this message]
2023-05-08 3:12 ` Jason Wang
2023-05-08 6:07 ` Michael S. Tsirkin
2023-05-08 6:13 ` Jason Wang
2023-05-08 6:47 ` Michael S. Tsirkin
2023-05-09 3:14 ` Jason Wang
2023-05-05 8:40 ` patchwork-bot+netdevbpf
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=20230507093328-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 \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xuanzhuo@linux.alibaba.com \
--cc=zhengqi.arch@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).