From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] config: remove NFP PMD from 32-bits builds
Date: Mon, 14 Jan 2019 18:12:54 +0000 [thread overview]
Message-ID: <20190114181254.27089-1-alejandro.lucero@netronome.com> (raw)
Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
---
config/defconfig_i686-native-linuxapp-gcc | 5 +++++
config/defconfig_i686-native-linuxapp-icc | 5 +++++
config/defconfig_x86_x32-native-linuxapp-gcc | 5 +++++
3 files changed, 15 insertions(+)
diff --git a/config/defconfig_i686-native-linuxapp-gcc b/config/defconfig_i686-native-linuxapp-gcc
index 1178fe35b..9b7086859 100644
--- a/config/defconfig_i686-native-linuxapp-gcc
+++ b/config/defconfig_i686-native-linuxapp-gcc
@@ -47,5 +47,10 @@ CONFIG_RTE_LIBRTE_PMD_ZUC=n
#
CONFIG_RTE_LIBRTE_AVP_PMD=n
+#
+# NFP PMD is not supported on 32-bit
+#
+CONFIG_RTE_LIBRTE_NFP_PMD=n
+
# 32-bit doesn't break up memory in lists, but does have VA allocation limit
CONFIG_RTE_MAX_MEM_MB=2048
diff --git a/config/defconfig_i686-native-linuxapp-icc b/config/defconfig_i686-native-linuxapp-icc
index 016c73f30..17defd803 100644
--- a/config/defconfig_i686-native-linuxapp-icc
+++ b/config/defconfig_i686-native-linuxapp-icc
@@ -47,5 +47,10 @@ CONFIG_RTE_LIBRTE_PMD_ZUC=n
#
CONFIG_RTE_LIBRTE_AVP_PMD=n
+#
+# NFP PMD is not supported on 32-bit
+#
+CONFIG_RTE_LIBRTE_NFP_PMD=n
+
# 32-bit doesn't break up memory in lists, but does have VA allocation limit
CONFIG_RTE_MAX_MEM_MB=2048
diff --git a/config/defconfig_x86_x32-native-linuxapp-gcc b/config/defconfig_x86_x32-native-linuxapp-gcc
index 57d000dc5..2c8419f14 100644
--- a/config/defconfig_x86_x32-native-linuxapp-gcc
+++ b/config/defconfig_x86_x32-native-linuxapp-gcc
@@ -27,5 +27,10 @@ CONFIG_RTE_LIBRTE_SFC_EFX_PMD=n
#
CONFIG_RTE_LIBRTE_AVP_PMD=n
+#
+# NFP PMD is not supported on 32-bit
+#
+CONFIG_RTE_LIBRTE_NFP_PMD=n
+
# 32-bit doesn't break up memory in lists, but does have VA allocation limit
CONFIG_RTE_MAX_MEM_MB=2048
--
2.17.1
next reply other threads:[~2019-01-14 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 18:12 Alejandro Lucero [this message]
2019-01-14 19:04 ` Thomas Monjalon
2019-01-15 10:39 ` Bruce Richardson
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=20190114181254.27089-1-alejandro.lucero@netronome.com \
--to=alejandro.lucero@netronome.com \
--cc=dev@dpdk.org \
/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).