From: Yongseok Koh <yskoh@mellanox.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org, olgas@mellanox.com, shahafs@mellanox.com, stable@dpdk.org
Subject: [dpdk-dev] [PATCH 1/3] doc: add mlx5 note for Bluefield build configuration
Date: Tue, 29 Jan 2019 23:53:19 -0800 [thread overview]
Message-ID: <20190130075321.24466-1-yskoh@mellanox.com> (raw)
Fixes: d14e4e976f65 ("config: add Mellanox BlueField armv8 SoC")
Cc: stable@dpdk.org
Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
---
doc/guides/nics/mlx5.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 3f168b1613..62de860d0a 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -221,6 +221,13 @@ These options can be modified in the ``.config`` file.
adds additional run-time checks and debugging messages at the cost of
lower performance.
+.. note::
+
+ For Bluefield, target should be set to ``arm64-bluefield-linuxapp-gcc``. This
+ will enable ``CONFIG_RTE_LIBRTE_MLX5_PMD`` and set ``RTE_CACHE_LINE_SIZE`` to
+ 64. Default armv8a configuration of make build and meson build set it to 128
+ then brings performance degradation.
+
Environment variables
~~~~~~~~~~~~~~~~~~~~~
--
2.11.0
next reply other threads:[~2019-01-30 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 7:53 Yongseok Koh [this message]
2019-01-30 7:53 ` [dpdk-dev] [PATCH 2/3] doc: add Mellanox EN support Yongseok Koh
2019-01-30 7:53 ` [dpdk-dev] [PATCH 3/3] doc: add mlx5 release note Yongseok Koh
2019-01-31 6:59 ` [dpdk-dev] [PATCH 1/3] doc: add mlx5 note for Bluefield build configuration Shahaf Shuler
2019-01-31 17:32 ` 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=20190130075321.24466-1-yskoh@mellanox.com \
--to=yskoh@mellanox.com \
--cc=dev@dpdk.org \
--cc=olgas@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--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).