From: Fady Bader <fady@mellanox.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, tbashar@mellanox.com, talshn@mellanox.com,
yohadt@mellanox.com, dmitry.kozliuk@gmail.com,
harini.ramakrishnan@microsoft.com, ocardona@microsoft.com,
pallavi.kadam@intel.com, ranjit.menon@intel.com,
olivier.matz@6wind.com, arybchenko@solarflare.com, mdr@ashroe.eu,
nhorman@tuxdriver.com
Subject: [dpdk-dev] [PATCH v2 3/4] eal: export needed functions for mempool
Date: Mon, 1 Jun 2020 13:31:38 +0300 [thread overview]
Message-ID: <20200601103139.8612-4-fady@mellanox.com> (raw)
In-Reply-To: <20200601103139.8612-1-fady@mellanox.com>
Some eal functions were used by mempool lib but not exported on Windows.
The function was exported.
Signed-off-by: Fady Bader <fady@mellanox.com>
---
lib/librte_eal/rte_eal_exports.def | 6 ++++++
lib/librte_eal/rte_eal_version.map | 3 +++
2 files changed, 9 insertions(+)
diff --git a/lib/librte_eal/rte_eal_exports.def b/lib/librte_eal/rte_eal_exports.def
index cbb6b8cfe..70d5e26b3 100644
--- a/lib/librte_eal/rte_eal_exports.def
+++ b/lib/librte_eal/rte_eal_exports.def
@@ -1,6 +1,11 @@
EXPORTS
__rte_panic
+ __rte_trace_mem_per_thread_alloc
+ __rte_trace_point_emit_field
+ __rte_trace_point_register
per_lcore__rte_errno
+ per_lcore_trace_mem
+ per_lcore_trace_point_sz
rte_calloc
rte_calloc_socket
rte_eal_get_configuration
@@ -49,6 +54,7 @@ EXPORTS
rte_memzone_walk
rte_vlog
rte_realloc
+ rte_strscpy
rte_zmalloc
rte_zmalloc_socket
diff --git a/lib/librte_eal/rte_eal_version.map b/lib/librte_eal/rte_eal_version.map
index 8937bdfea..b96b21220 100644
--- a/lib/librte_eal/rte_eal_version.map
+++ b/lib/librte_eal/rte_eal_version.map
@@ -393,4 +393,7 @@ EXPERIMENTAL {
rte_mem_map;
rte_mem_unmap;
__emutls_v.per_lcore__rte_errno;
+ __emutls_v.per_lcore_trace_mem;
+ __emutls_v.per_lcore_trace_point_sz;
+ __rte_trace_mem_per_thread_alloc;
};
--
2.16.1.windows.4
next prev parent reply other threads:[~2020-06-01 10:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 10:31 [dpdk-dev] [PATCH v2 0/4] build mempool on Windows Fady Bader
2020-06-01 10:31 ` [dpdk-dev] [PATCH v2 1/4] eal: disable function versioning " Fady Bader
2020-06-01 19:55 ` Neil Horman
2020-06-01 21:46 ` [dpdk-dev] [EXTERNAL] " Omar Cardona
2020-06-02 10:27 ` Neil Horman
2020-06-02 10:40 ` Thomas Monjalon
2020-06-11 10:09 ` Kinsella, Ray
2020-06-01 10:31 ` [dpdk-dev] [PATCH v2 2/4] mempool: use generic memory management Fady Bader
2020-06-01 19:59 ` Dmitry Kozlyuk
2020-06-01 20:47 ` Ranjit Menon
2020-06-01 21:14 ` Thomas Monjalon
2020-06-02 7:40 ` Andrew Rybchenko
2020-06-01 10:31 ` Fady Bader [this message]
2020-06-01 10:31 ` [dpdk-dev] [PATCH v2 4/4] mempool: mempool build on Windows Fady Bader
2020-06-02 7:41 ` Andrew Rybchenko
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=20200601103139.8612-4-fady@mellanox.com \
--to=fady@mellanox.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=harini.ramakrishnan@microsoft.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.com \
--cc=ocardona@microsoft.com \
--cc=olivier.matz@6wind.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=talshn@mellanox.com \
--cc=tbashar@mellanox.com \
--cc=thomas@monjalon.net \
--cc=yohadt@mellanox.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).