From: Stephen Hemminger <stephen@networkplumber.org>
To: Reshma Pattan <reshma.pattan@intel.com>
Cc: dev@dpdk.org, david.hunt@intel.com, liang.j.ma@intel.com,
anatoly.burakov@intel.com
Subject: Re: [dpdk-dev] [PATCH v1] examples/l3fwd-power: add telemetry mode support
Date: Wed, 22 May 2019 08:16:57 -0700 [thread overview]
Message-ID: <20190522081657.52fb6e42@hermes.lan> (raw)
In-Reply-To: <20190517181712.12027-1-reshma.pattan@intel.com>
On Fri, 17 May 2019 19:17:12 +0100
Reshma Pattan <reshma.pattan@intel.com> wrote:
> Add new telemetry mode support for l3fwd-power.
> This is a standalone mode, in this mode l3fwd-power
> does simple l3fwding along with calculating
> empty polls, full polls, and busy percentage for
> each forwarding core. The aggregation of these
> values of all cores is reported as application
> level telemetry to metric library for every 10ms from the
> master core.
>
> The busy percentage is calculated by recording the poll_count
> and when the count reaches a defined value the total
> cycles it took is measured and compared with minimum and maximum
> reference cycles and busy rate is set according to either 0% or
> 50% or 100%.
>
> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
I think this adding more complexity to an example, which makes it harder
not easier for users. The existing l3fwd-power has grown too large
already and needs some architecture refactoring anyway.
next prev parent reply other threads:[~2019-05-22 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 18:17 Reshma Pattan
2019-05-20 13:17 ` Burakov, Anatoly
2019-05-21 14:53 ` Pattan, Reshma
2019-05-22 9:46 ` Burakov, Anatoly
2019-05-22 13:06 ` Pattan, Reshma
2019-05-22 15:16 ` Stephen Hemminger [this message]
2019-05-24 9:34 ` [dpdk-dev] [PATCH v2] " Reshma Pattan
2019-05-24 10:14 ` Burakov, Anatoly
2019-06-13 13:44 ` [dpdk-dev] [PATCH v3] " Reshma Pattan
2019-06-24 15:16 ` Thomas Monjalon
2019-06-24 16:48 ` Pattan, Reshma
2019-06-24 16:45 ` [dpdk-dev] [PATCH v4] " Reshma Pattan
2019-06-28 9:53 ` 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=20190522081657.52fb6e42@hermes.lan \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=liang.j.ma@intel.com \
--cc=reshma.pattan@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).