From: Vipin Varghese <vipin.varghese@intel.com>
To: dev@dpdk.org, john.mcnamara@intel.com
Cc: marko.kovacevic@intel.com, Vipin Varghese <vipin.varghese@intel.com>
Subject: [dpdk-dev] [PATCH v3] doc: update the usage for shared library
Date: Thu, 8 Feb 2018 23:49:59 +0530 [thread overview]
Message-ID: <1518113999-23539-1-git-send-email-vipin.varghese@intel.com> (raw)
In-Reply-To: <1517926143-16585-1-git-send-email-vipin.varghese@intel.com>
Add note information to intimate about use of option '-d' for shared
library in DPDK application.
Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
---
V3 Changes:
- updated from 'dpdk-testpmd' to 'testpmd' - John
V2 Changes:
- updated the space - John
- updated testpmd to dpdk-testpmd - John
---
doc/guides/nics/build_and_test.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guides/nics/build_and_test.rst b/doc/guides/nics/build_and_test.rst
index 62ac52c..d9a78ee 100644
--- a/doc/guides/nics/build_and_test.rst
+++ b/doc/guides/nics/build_and_test.rst
@@ -151,3 +151,7 @@ This section demonstrates how to setup and run ``testpmd`` in Linux.
Refer to the :ref:`testpmd runtime functions <testpmd_runtime>` for a list
of available commands.
+
+ .. note::
+ When ``testpmd`` is built with shared library, use option ``-d`` to load
+ the dynamic PMD for ``rte_eal_init``.
--
1.9.1
next prev parent reply other threads:[~2018-02-08 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 14:17 [dpdk-dev] [PATCH] " Vipin Varghese
2018-02-06 12:17 ` Mcnamara, John
2018-02-06 14:09 ` [dpdk-dev] [PATCH v2] " Vipin Varghese
2018-02-06 15:31 ` Mcnamara, John
2018-02-08 18:19 ` Vipin Varghese [this message]
2018-02-09 9:19 ` [dpdk-dev] [PATCH v3] " Mcnamara, John
2018-02-13 23:05 ` 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=1518113999-23539-1-git-send-email-vipin.varghese@intel.com \
--to=vipin.varghese@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@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).