From: Paolo Abeni <pabeni@redhat.com>
To: Wenliang Wang <wangwenliang.1995@bytedance.com>,
mst@redhat.com, jasowang@redhat.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, zhengqi.arch@bytedance.com,
willemdebruijn.kernel@gmail.com
Cc: virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] virtio_net: suppress cpu stall when free_unused_bufs
Date: Tue, 02 May 2023 11:05:40 +0200 [thread overview]
Message-ID: <d05564fd4fc47ed212be2c02be4d7c05167fa2b3.camel@redhat.com> (raw)
In-Reply-To: <1682783278-12819-1-git-send-email-wangwenliang.1995@bytedance.com>
On Sat, 2023-04-29 at 23:47 +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>
Net next is currently closed, but this patch could arguably land on the
net tree - assuming Micheal agrees.
In that case you should include a suitable Fixes tag - reposting a new
version.
> ---
> v2:
> -add need_resched check.
> -apply same logic to sq.
> v3:
> -use cond_resched instead.
> ---
> 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 ea1bd4bb326d..744bdc8a1abd 100644
> --- a/drivers/net/virtio_net.c
> +++ b/drivers/net/virtio_net.c
> @@ -3559,12 +3559,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();
Note that on v1 Xuan Zhuo suggested to do the above check only every a
low fixed number of buffer. I think the current code is a better
option, as the need_resched() check is very cheap and the overall code
simpler.
In any case, when submitting a new revision, please explicitly CC
whoever gave feedback on previous ones.
Thanks,
Paolo
prev parent reply other threads:[~2023-05-02 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 15:47 Wenliang Wang
2023-05-02 9:05 ` Paolo Abeni [this message]
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=d05564fd4fc47ed212be2c02be4d7c05167fa2b3.camel@redhat.com \
--to=pabeni@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=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wangwenliang.1995@bytedance.com \
--cc=willemdebruijn.kernel@gmail.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
all inboxes | Powered by JetHome®