From: Reshma Pattan <reshma.pattan@intel.com>
To: john.mcnamara@intel.com, dev@dpdk.org
Cc: Reshma Pattan <reshma.pattan@intel.com>
Subject: [dpdk-dev] [PATCH] doc: update eal option usage for FreeBSD
Date: Thu, 26 Apr 2018 16:48:07 +0100 [thread overview]
Message-ID: <1524757687-18218-1-git-send-email-reshma.pattan@intel.com> (raw)
EAL option -m is supported in FreeBSD,
so move it under supported heading from non
supported heading.
Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
---
doc/guides/freebsd_gsg/build_sample_apps.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/guides/freebsd_gsg/build_sample_apps.rst b/doc/guides/freebsd_gsg/build_sample_apps.rst
index 90f050232..ac92260f1 100644
--- a/doc/guides/freebsd_gsg/build_sample_apps.rst
+++ b/doc/guides/freebsd_gsg/build_sample_apps.rst
@@ -128,6 +128,10 @@ The EAL options for FreeBSD are as follows:
* ``--proc-type``:
The type of process instance.
+* ``-m MB``:
+ Memory to allocate from hugepages, regardless of processor socket.
+ It is recommended that ``--socket-mem`` be used instead of this option.
+
Other options, specific to Linux and are not supported under FreeBSD are as follows:
* ``socket-mem``:
@@ -142,10 +146,6 @@ Other options, specific to Linux and are not supported under FreeBSD are as foll
* ``--file-prefix``:
The prefix text used for hugepage filenames.
-* ``-m MB``:
- Memory to allocate from hugepages, regardless of processor socket.
- It is recommended that ``--socket-mem`` be used instead of this option.
-
The ``-c`` or ``-l`` option is mandatory; the others are optional.
Copy the DPDK application binary to your target, then run the application
--
2.14.3
next reply other threads:[~2018-04-26 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 15:48 Reshma Pattan [this message]
2018-04-27 9:20 ` Burakov, Anatoly
2018-04-27 9:22 ` Pattan, Reshma
2018-04-27 12:59 ` [dpdk-dev] [PATCH v2] " Reshma Pattan
2018-04-27 13:14 ` Burakov, Anatoly
2018-04-27 22:08 ` 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=1524757687-18218-1-git-send-email-reshma.pattan@intel.com \
--to=reshma.pattan@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).