From: Thomas Monjalon <thomas@monjalon.net>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: dev@dpdk.org, dmitry.kozliuk@gmail.com,
navasile@linux.microsoft.com, ciara.power@intel.com,
bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] metrics/windows: build rte_metrics library
Date: Tue, 19 Jan 2021 22:52:03 +0100 [thread overview]
Message-ID: <5601419.A6MszWdEHB@thomas> (raw)
In-Reply-To: <20210119213125.GA1983@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
19/01/2021 22:31, Tyler Retzlaff:
> On Sun, Jan 17, 2021 at 11:19:55PM +0100, Thomas Monjalon wrote:
> >
> > Not sure it makes sense without the new telemetry feature.
> > Please focus on telemetry lib instead of half-enabling
> > the old metrics lib.
> >
>
> can you elaborate? (or reference a mailing list discussion) that gives some
> guidance?
>
> is the telemetry lib a replacement for metrics? the component we have now
> relies on the non-telemetry functions exported from metrics but does not
> use the telemetry functions.
>
> also, i notice that the meson.build for telemetry lib has an include path
> that references rte_metrics but does not appear to actually include any of
> the headers from rte_metrics (vestigial? missed in previous cleanup perhaps?)
I think Bruce and Ciara will better explain than me
the intent of the telemetry lib and the compatibility path with the metrics lib.
next prev parent reply other threads:[~2021-01-19 21:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 23:37 [dpdk-dev] [PATCH] metrics/windows: build rte_metrics library Tyler Retzlaff
2021-01-12 1:15 ` Dmitry Kozlyuk
2021-01-12 1:32 ` Tyler Retzlaff
2021-01-12 6:44 ` Tal Shnaiderman
2021-01-12 1:30 ` [dpdk-dev] [PATCH v2] " Tyler Retzlaff
2021-01-17 22:19 ` Thomas Monjalon
2021-01-19 21:31 ` Tyler Retzlaff
2021-01-19 21:52 ` Thomas Monjalon [this message]
2021-01-20 10:37 ` Bruce Richardson
2021-01-20 11:09 ` Thomas Monjalon
2021-01-20 11:54 ` Bruce Richardson
2021-01-20 12:13 ` Thomas Monjalon
2021-01-20 13:57 ` Bruce Richardson
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=5601419.A6MszWdEHB@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=navasile@linux.microsoft.com \
--cc=roretzla@linux.microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.