DPDK patches and discussions
 help / color / mirror / Atom feed
From: Remy Horton <remy.horton@intel.com>
To: wanjunjie <wan.junjie@foxmail.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4] lib/metrics: add unregister api for metrics
Date: Tue, 26 Feb 2019 16:10:37 +0000	[thread overview]
Message-ID: <62e80592-dd86-7b59-5c09-b19c0a413325@intel.com> (raw)
In-Reply-To: <1550849955-15101-1-git-send-email-wan.junjie@foxmail.com>

This patch has checkpatch errors that will need to be fixed:

ERROR:SPACING: space prohibited before that close parenthesis ')'
#179: FILE: lib/librte_metrics/rte_metrics.c:233:
+       if (count < 1 )

ERROR:TRAILING_WHITESPACE: trailing whitespace
#242: FILE: lib/librte_metrics/rte_metrics.c:298:
+^I^Ifor (idx_name = 0; idx < stats->cnt_stats && $


If the patch is applied, two of the unit-tests for metrics break:

# ./test/build/app/test
RTE>>metrics_autotest
  + ------------------------------------------------------- +
  + Test Suite : Metrics Unit Test Suite
  + ------------------------------------------------------- +
  + TestCase [ 0] : test_metrics_without_init succeeded
  + TestCase [ 1] : test_metrics_reg_name_with_validname succeeded
  + TestCase [ 2] : test_metrics_reg_names succeeded
  + TestCase [ 3] : test_metrics_update_value failed
  + TestCase [ 4] : test_metrics_update_values failed
  + TestCase [ 5] : test_metrics_get_names succeeded
  + TestCase [ 6] : test_metrics_get_values succeeded
  + ------------------------------------------------------- +
  + Test Suite Summary
  + Tests Total :        7
  + Tests Skipped :      0
  + Tests Executed :     7
  + Tests Unsupported:   0
  + Tests Passed :       5
  + Tests Failed :       2
  + ------------------------------------------------------- +


Both of these issues will need to be addressed.


On 22/02/2019 15:39, wanjunjie wrote:
> From: junka <wan.junjie@foxmail.com>
>
> The bitmap will help maintain the metrics. We can dynamically
> add and remove metrics data. For example, after uninit latency lib,
> it could remove itself from the metrics. This could make the result
> from rte_metrics_get_names much more simple to display the wanted
> metrics data only.
>
> Signed-off-by: junka <wan.junjie@foxmail.com>
> ---
>  lib/librte_metrics/rte_metrics.c | 182 ++++++++++++++++++++++++++++-----------
>  lib/librte_metrics/rte_metrics.h |  21 +++++
>  2 files changed, 152 insertions(+), 51 deletions(-)

<snip>

  reply	other threads:[~2019-02-26 16:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22  6:16 [dpdk-dev] [PATCH] "  =?gb18030?B?zfK/ob3c?=
2019-02-22 13:56 ` [dpdk-dev] [PATCH v2] " wanjunjie
2019-02-22 15:03   ` [dpdk-dev] [PATCH v3] " wanjunjie
2019-02-22 15:39     ` [dpdk-dev] [PATCH v4] " wanjunjie
2019-02-26 16:10       ` Remy Horton [this message]
2019-02-27 17:19       ` [dpdk-dev] [PATCH v5] " Junjie Wan
2019-02-28 11:53         ` Remy Horton
2019-02-28 13:28           ` Wan Junjie
2019-02-28 13:55             ` Remy Horton
2019-04-02  0:27         ` Thomas Monjalon
2019-04-02  0:27           ` Thomas Monjalon
2019-04-02  0:30           ` Thomas Monjalon
2019-04-02  0:30             ` Thomas Monjalon

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=62e80592-dd86-7b59-5c09-b19c0a413325@intel.com \
    --to=remy.horton@intel.com \
    --cc=dev@dpdk.org \
    --cc=wan.junjie@foxmail.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).