DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Edwin Brossette <edwin.brossette@6wind.com>, dev@dpdk.org
Cc: Olivier Matz <olivier.matz@6wind.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: net/virtio: duplicated xstats
Date: Mon, 27 Nov 2023 10:22:10 +0000	[thread overview]
Message-ID: <6b76373b-c97a-4605-be89-271eddea4af6@amd.com> (raw)
In-Reply-To: <ab77c325-4be5-4d53-9120-da6ac3f98cbf@amd.com>

On 11/27/2023 10:19 AM, Ferruh Yigit wrote:
> On 11/24/2023 9:18 AM, Edwin Brossette wrote:
>> Hello,
>>
>> I noticed a small inconsistency in the virtio pmd's xstats.
>> The stat "rx_q0_errors" appears twice.
>> I also think the stats "rx_q0_packets", "rx_q0_bytes", "tx_q0_packets"
>> and "tx_q0_bytes" are duplicates of "rx_q0_good_packets",
>> "rx_q0_good_bytes", "tx_q0_good_packets" and "tx_q0_good_bytes"
>>
> 
> Ack, I didn't reproduce but from code I can see this inconsistency can
> occur.
> 
> 
>> I believe this issue probably appeared after this commit:
>>
>> f30e69b41f94: ethdev: add device flag to bypass auto-filled queue xstats
>> http://scm.6wind.com/vendor/dpdk.org/dpdk/commit/?id=f30e69b41f949cd4a9afb6ff39de196e661708e2 <http://scm.6wind.com/vendor/dpdk.org/dpdk/commit/?id=f30e69b41f949cd4a9afb6ff39de196e661708e2>
>>
>> From what I understand, the rxq0_error stat was originally reported by
>> the librte. However, changes were made so it is reported by the pmd instead.
>> The flag RTE_ETH_DEV_AUTOFILL_QUEUE_XSTATS was temporarily set to keep
>> the old behaviour so that every pmd could have time to adapt the change.
>> But it seems the flag was forgotten in the virtio pmd and as a result,
>> some stats are fetched at two different times when displaying xstats.
>>
> 
> Motivation is move queue stats from "basic stats" to "xstats".
> 
> 'RTE_ETH_DEV_AUTOFILL_QUEUE_XSTATS' is a temporary flag, as you said,
> and when driver sets it, ethdev layer copies queue stats from basic
> stats to xstats.
> In long term expectation is driver itself implement queue stats in
> xstats and unset the flag, when all drivers implement this, flag will be
> removed.
> 
> 
> The issue with virtio is it already has queue stats in the xstats, with
> the flag some queue stats duplicated.
> It seems it is not forgotten to be removed, but it was mistake to add
> flag at first place. So OK to remove the flag from virtio PMD.
> 

Fixed Maxime's email.


      reply	other threads:[~2023-11-27 10:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24  9:18 Edwin Brossette
2023-11-24  9:26 ` Olivier Matz
2023-11-24 10:39   ` Maxime Coquelin
2023-11-24 13:13     ` Edwin Brossette
2023-11-24 13:16       ` Maxime Coquelin
2023-11-24 13:52 ` [PATCH] net/virtio: fix duplicated rxq xstats edwin.brossette
2023-11-27 10:20   ` Ferruh Yigit
2024-02-06 14:56   ` Maxime Coquelin
2023-11-27 10:19 ` net/virtio: duplicated xstats Ferruh Yigit
2023-11-27 10:22   ` Ferruh Yigit [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=6b76373b-c97a-4605-be89-271eddea4af6@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=edwin.brossette@6wind.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=olivier.matz@6wind.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).