From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: dev@dpdk.org, thomas@monjalon.net,
Pallavi Kadam <pallavi.kadam@intel.com>,
Khoa To <khot@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH] metrics/windows: build rte_metrics library
Date: Tue, 12 Jan 2021 04:15:34 +0300 [thread overview]
Message-ID: <20210112041534.1402eaa3@sovereign> (raw)
In-Reply-To: <1610408246-29482-1-git-send-email-roretzla@linux.microsoft.com>
+ Pallavi, Khoa
On Mon, 11 Jan 2021 15:37:26 -0800, Tyler Retzlaff wrote:
> From: Tyler Retzlaff <roretzla@microsoft.com>
>
> declare reduced set of exports for rte_metrics on windows and include
> it in the set of libraries to build and install.
>
> rte_metrics_tel* exports depend on conditionally available component.
> this change minimally allows enabling the building of rte_metrics on
> windows.
What's the future plan? Once we talked about a script that would inspect
objects and filter missing functions from the list in .map to build .def. Is
MSFT working on it? Or do we choose another way?
> --- /dev/null
> +++ b/lib/librte_metrics/rte_metrics_exports.def
> @@ -0,0 +1,8 @@
> +EXPORTS
> + rte_metrics_get_names
> + rte_metrics_get_values
> + rte_metrics_init
+ rte_metrics_deinit
> + rte_metrics_reg_name
> + rte_metrics_reg_names
> + rte_metrics_update_value
> + rte_metrics_update_values
next prev parent reply other threads:[~2021-01-12 1:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 23:37 Tyler Retzlaff
2021-01-12 1:15 ` Dmitry Kozlyuk [this message]
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
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=20210112041534.1402eaa3@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=khot@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=roretzla@linux.microsoft.com \
--cc=thomas@monjalon.net \
/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).