From: Jakub Kicinski <kuba@kernel.org>
To: Li RongQing <lirongqing@baidu.com>
Cc: mst@redhat.com, jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
eperezma@redhat.com, hengqi@linux.alibaba.com,
virtualization@lists.linux.dev, netdev@vger.kernel.org
Subject: Re: [PATCH] virtio_net: Use u64_stats_fetch_begin() for stats fetch
Date: Thu, 20 Jun 2024 07:09:08 -0700 [thread overview]
Message-ID: <20240620070908.2efe2048@kernel.org> (raw)
In-Reply-To: <20240619025529.5264-1-lirongqing@baidu.com>
On Wed, 19 Jun 2024 10:55:29 +0800 Li RongQing wrote:
> This place is fetching the stats, so u64_stats_fetch_begin
> and u64_stats_fetch_retry should be used
>
> Fixes: 6208799553a8 ("virtio-net: support rx netdim")
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
> ---
> drivers/net/virtio_net.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> index 61a57d1..b669e73 100644
> --- a/drivers/net/virtio_net.c
> +++ b/drivers/net/virtio_net.c
> @@ -2332,16 +2332,18 @@ static void virtnet_poll_cleantx(struct receive_queue *rq)
> static void virtnet_rx_dim_update(struct virtnet_info *vi, struct receive_queue *rq)
> {
> struct dim_sample cur_sample = {};
> + unsigned int start;
>
> if (!rq->packets_in_napi)
> return;
>
> - u64_stats_update_begin(&rq->stats.syncp);
> - dim_update_sample(rq->calls,
> - u64_stats_read(&rq->stats.packets),
> - u64_stats_read(&rq->stats.bytes),
> - &cur_sample);
> - u64_stats_update_end(&rq->stats.syncp);
> + do {
> + start = u64_stats_fetch_begin(&rq->stats.syncp);
> + dim_update_sample(rq->calls,
> + u64_stats_read(&rq->stats.packets),
> + u64_stats_read(&rq->stats.bytes),
> + &cur_sample);
> + } while (u64_stats_fetch_retry(&rq->stats.syncp, start));
Did you by any chance use an automated tool of any sort to find this
issue or generate the fix?
I don't think this is actually necessary here, you're in the same
context as the updater of the stats, you don't need any protection.
You can remove u64_stats_update_begin() / end() (in net-next, there's
no bug).
I won't comment on implications of calling dim_update_sample() in
a loop.
Please make sure you answer my "did you use a tool" question, I'm
really curious.
--
pw-bot: cr
next prev parent reply other threads:[~2024-06-20 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 2:55 [PATCH] virtio_net: Use u64_stats_fetch_begin() for stats fetch Li RongQing
2024-06-19 7:42 ` Heng Qi
2024-06-19 8:06 ` Jiri Pirko
2024-06-19 8:34 ` Michael S. Tsirkin
2024-06-20 0:33 ` Jason Wang
2024-06-20 14:09 ` Jakub Kicinski [this message]
2024-06-20 15:52 ` Michael S. Tsirkin
2024-06-21 6:20 ` [????] " Li,Rongqing
2024-07-09 12:45 ` Michael S. Tsirkin
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=20240620070908.2efe2048@kernel.org \
--to=kuba@kernel.org \
--cc=eperezma@redhat.com \
--cc=hengqi@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=lirongqing@baidu.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.