From: Remy Horton <remy.horton@intel.com>
To: Junjie Wan <wan.junjie@foxmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v5] lib/metrics: add unregister api for metrics
Date: Thu, 28 Feb 2019 11:53:19 +0000 [thread overview]
Message-ID: <dd2cad43-31ab-89be-bc70-1a36c7822459@intel.com> (raw)
In-Reply-To: <1551287944-27314-1-git-send-email-wan.junjie@foxmail.com>
The tests for metrics themselves now all pass, but there is failure with
bitrate statistics (bitrate stats uses metrics underneath). Latency
statistics, which also uses metrics, seems ok though.
RTE>>bitratestats_autotest
+ ------------------------------------------------------- +
+ Test Suite : BitRate Stats Unit Test Suite
port in ring setup : 0
+ ------------------------------------------------------- +
+ TestCase [ 0] : test_stats_bitrate_create succeeded
+ TestCase [ 1] : test_stats_bitrate_reg failed
+ TestCase [ 2] : test_stats_bitrate_reg_invalidpointer succeeded
+ TestCase [ 3] : test_stats_bitrate_calc_invalid_bitrate_data succeeded
Invalid port_id=33
+ TestCase [ 4] : test_stats_bitrate_calc_invalid_portid_1 succeeded
Invalid port_id=65535
+ TestCase [ 5] : test_stats_bitrate_calc_invalid_portid_2 succeeded
Invalid port_id=31
+ TestCase [ 6] : test_stats_bitrate_calc_non_existing_portid succeeded
+ TestCase [ 7] : test_stats_bitrate_calc succeeded
+ ------------------------------------------------------- +
+ Test Suite Summary
+ Tests Total : 8
+ Tests Skipped : 0
+ Tests Executed : 8
+ Tests Unsupported: 0
+ Tests Passed : 7
+ Tests Failed : 1
+ ------------------------------------------------------- +
Test Failed
Personally if I was reimplementing metrics I would be inclined to
replace the single fixed-size metadata[] array that is carved up with
something more dynamic, perhaps a 2d linked-list. Doing so would
probably negate the need for a bitmap.
On 27/02/2019 17:19, Junjie Wan 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: Junjie Wan <wan.junjie@foxmail.com>
next prev parent reply other threads:[~2019-02-28 11:53 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
2019-02-27 17:19 ` [dpdk-dev] [PATCH v5] " Junjie Wan
2019-02-28 11:53 ` Remy Horton [this message]
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=dd2cad43-31ab-89be-bc70-1a36c7822459@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).