From: Vipin Varghese <vipin.varghese@intel.com>
To: dev@dpdk.org, marko.kovacevic@intel.com, john.mcnamara@intel.com,
thomas@monjalon.net
Cc: sanjay.padubidri@intel.com, Vipin Varghese <vipin.varghese@intel.com>
Subject: [dpdk-dev] [PATCH v2] doc/testpmd: update compile steps for bpf examples
Date: Thu, 23 May 2019 19:17:44 +0530 [thread overview]
Message-ID: <20190523134744.73755-1-vipin.varghese@intel.com> (raw)
In-Reply-To: <20190507084112.35296-1-vipin.varghese@intel.com>
Add note in the missing arguments for compiling BPF examples.
Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
---
V2:
- ACK for documentation - John McNamara
- move to compile section - Thomas Monjalon
---
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
index cb83a3ce8..88a66b9a8 100644
--- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
+++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
@@ -4651,6 +4651,10 @@ For example:
cd examples/bpf
clang -O2 -target bpf -c t1.c
+.. note::
+
+ To built other BPF examples, the compiler requires additional command-line options.
+
Then to load (and JIT compile) t1.o at RX queue 0, port 1:
.. code-block:: console
--
2.17.1
next prev parent reply other threads:[~2019-05-23 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 8:41 [dpdk-dev] [PATCH] doc/testpmd: update compile steps for bpf examples Vipin Varghese
2019-05-07 15:07 ` Mcnamara, John
2019-05-09 22:31 ` Thomas Monjalon
2019-05-10 1:41 ` Varghese, Vipin
2019-05-23 13:47 ` Vipin Varghese [this message]
2019-05-29 11:17 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2019-05-30 15:40 ` Varghese, Vipin
2019-06-10 5:41 ` [dpdk-dev] [PATCH v3] " Vipin Varghese
2023-06-12 16:31 ` Stephen Hemminger
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=20190523134744.73755-1-vipin.varghese@intel.com \
--to=vipin.varghese@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=sanjay.padubidri@intel.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 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.