DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Min Hu (Connor)" <humin29@huawei.com>
To: "Singh, Aman Deep" <aman.deep.singh@intel.com>, <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <xiaoyun.li@intel.com>, <yuying.zhang@intel.com>
Subject: Re: [PATCH 1/2] app/testpmd: fix stats get when display fwd stats
Date: Thu, 28 Apr 2022 11:10:10 +0800	[thread overview]
Message-ID: <fe8f0583-a0d6-efd2-96f6-6488cef2be2c@huawei.com> (raw)
In-Reply-To: <24445fab-6aa3-a8e0-0faa-e32b8ddb2eef@intel.com>

Hi, Singh,

在 2022/4/27 20:15, Singh, Aman Deep 写道:
> 
> 
> On 4/6/2022 2:15 PM, Min Hu (Connor) wrote:
>> In function 'fwd_stats_display', if function 'rte_eth_stats_get' fails,
>> 'stats' is uncertainty value. The display result will be abnormal.
>>
>> This patch check the return value of 'rte_eth_stats_get' to avoid
>> display abnormal stats.
>>
>> Fixes: 53324971a14e ("app/testpmd: display/clear forwarding stats on 
>> demand")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
>> ---
>>   app/test-pmd/config.c  | 10 ++++++++--
>>   app/test-pmd/testpmd.c | 16 ++++++++++++++--
>>   2 files changed, 22 insertions(+), 4 deletions(-)
>>
>> diff --git a/app/test-pmd/config.c b/app/test-pmd/config.c
>> index cc8e7aa138..bd689f9f86 100644
>> --- a/app/test-pmd/config.c
>> +++ b/app/test-pmd/config.c
>> @@ -249,14 +249,20 @@ nic_stats_display(portid_t port_id)
>>                                   diff_ns;
>>       uint64_t mpps_rx, mpps_tx, mbps_rx, mbps_tx;
>>       struct rte_eth_stats stats;
>> -
>>       static const char *nic_stats_border = "########################";
>> +    int ret;
>>       if (port_id_is_invalid(port_id, ENABLED_WARN)) {
>>           print_valid_ports();
>>           return;
>>       }
>> -    rte_eth_stats_get(port_id, &stats);
>> +    ret = rte_eth_stats_get(port_id, &stats);
>> +    if (ret != 0) {
>> +        fprintf(stderr,
>> +            "%s: Error: failed to get stats (port %u): %d",
>> +            __func__, port_id, ret);
>> +        return;
>> +    }
>>       printf("\n  %s NIC statistics for port %-2d %s\n",
>>              nic_stats_border, port_id, nic_stats_border);
>> diff --git a/app/test-pmd/testpmd.c b/app/test-pmd/testpmd.c
>> index fe2ce19f99..79bb23264b 100644
>> --- a/app/test-pmd/testpmd.c
>> +++ b/app/test-pmd/testpmd.c
>> @@ -1982,6 +1982,7 @@ fwd_stats_display(void)
>>       struct rte_port *port;
>>       streamid_t sm_id;
>>       portid_t pt_id;
>> +    int ret;
>>       int i;
>>       memset(ports_stats, 0, sizeof(ports_stats));
>> @@ -2013,7 +2014,13 @@ fwd_stats_display(void)
>>           pt_id = fwd_ports_ids[i];
>>           port = &ports[pt_id];
>> -        rte_eth_stats_get(pt_id, &stats);
>> +        ret = rte_eth_stats_get(pt_id, &stats);
>> +        if (ret != 0) {
>> +            fprintf(stderr,
>> +                "%s: Error: failed to get stats (port %u): %d",
>> +                __func__, pt_id, ret);
>> +            continue;
>> +        }
>>           stats.ipackets -= port->stats.ipackets;
>>           stats.opackets -= port->stats.opackets;
>>           stats.ibytes -= port->stats.ibytes;
>> @@ -2108,11 +2115,16 @@ fwd_stats_reset(void)
>>   {
>>       streamid_t sm_id;
>>       portid_t pt_id;
>> +    int ret;
>>       int i;
>>       for (i = 0; i < cur_fwd_config.nb_fwd_ports; i++) {
>>           pt_id = fwd_ports_ids[i];
>> -        rte_eth_stats_get(pt_id, &ports[pt_id].stats);
>> +        ret = rte_eth_stats_get(pt_id, &ports[pt_id].stats);
>> +        if (ret != 0)
>> +            fprintf(stderr,
>> +                "%s: Error: failed to clear stats (port %u):%d",
>> +                __func__, pt_id, ret);
> Should we clear "ports[pt_id].stats" in this condition.
when done 'rte_eth_stats_get',
if success, 'ports[pt_id].stats' will be cleared in this function.
if failed, no need to clear 'ports[pt_id].stats' as the log said.

>>       }
>>       for (sm_id = 0; sm_id < cur_fwd_config.nb_fwd_streams; sm_id++) {
>>           struct fwd_stream *fs = fwd_streams[sm_id];
> As such LGTM
Thanks for your comment.
> Acked-by: Aman Singh <aman.deep.singh@intel.com>
> .

  reply	other threads:[~2022-04-28  3:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  8:45 [PATCH 0/2] bugfix for testpmd Min Hu (Connor)
2022-04-06  8:45 ` [PATCH 1/2] app/testpmd: fix stats get when display fwd stats Min Hu (Connor)
2022-04-27 12:15   ` Singh, Aman Deep
2022-04-28  3:10     ` Min Hu (Connor) [this message]
2022-04-06  8:45 ` [PATCH 2/2] app/testpmd: fix incorrect MTU verification Min Hu (Connor)
2022-04-25 16:25   ` Singh, Aman Deep
2022-04-26  1:38     ` lihuisong (C)
2022-05-12 16:37       ` Ferruh Yigit
2022-04-25  6:52 ` [PATCH 0/2] bugfix for testpmd Min Hu (Connor)
2022-05-12 16:37   ` Ferruh Yigit

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=fe8f0583-a0d6-efd2-96f6-6488cef2be2c@huawei.com \
    --to=humin29@huawei.com \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=xiaoyun.li@intel.com \
    --cc=yuying.zhang@intel.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).