DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com, Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: [dpdk-dev] [PATCH v2 3/3] config: enable the thunderx nicvf driver
Date: Sun, 12 Mar 2017 19:32:32 +0530	[thread overview]
Message-ID: <1489327352-31938-3-git-send-email-jerin.jacob@caviumnetworks.com> (raw)
In-Reply-To: <1489327352-31938-1-git-send-email-jerin.jacob@caviumnetworks.com>

Enable Thunderx nicvf PMD driver in the common
config as it does not have build dependency
with any external library and/or architecture.

Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
---
 config/common_base                           |  2 +-
 config/defconfig_arm64-thunderx-linuxapp-gcc | 10 ----------
 doc/guides/nics/thunderx.rst                 |  3 +--
 3 files changed, 2 insertions(+), 13 deletions(-)

diff --git a/config/common_base b/config/common_base
index aeee13e..e48417d 100644
--- a/config/common_base
+++ b/config/common_base
@@ -279,7 +279,7 @@ CONFIG_RTE_LIBRTE_PMD_SZEDATA2_AS=0
 #
 # Compile burst-oriented Cavium Thunderx NICVF PMD driver
 #
-CONFIG_RTE_LIBRTE_THUNDERX_NICVF_PMD=n
+CONFIG_RTE_LIBRTE_THUNDERX_NICVF_PMD=y
 CONFIG_RTE_LIBRTE_THUNDERX_NICVF_DEBUG_INIT=n
 CONFIG_RTE_LIBRTE_THUNDERX_NICVF_DEBUG_RX=n
 CONFIG_RTE_LIBRTE_THUNDERX_NICVF_DEBUG_TX=n
diff --git a/config/defconfig_arm64-thunderx-linuxapp-gcc b/config/defconfig_arm64-thunderx-linuxapp-gcc
index a5b1e24..9818a2e 100644
--- a/config/defconfig_arm64-thunderx-linuxapp-gcc
+++ b/config/defconfig_arm64-thunderx-linuxapp-gcc
@@ -36,13 +36,3 @@ CONFIG_RTE_MACHINE="thunderx"
 CONFIG_RTE_CACHE_LINE_SIZE=128
 CONFIG_RTE_MAX_NUMA_NODES=2
 CONFIG_RTE_MAX_LCORE=96
-
-#
-# Compile Cavium Thunderx NICVF PMD driver
-#
-CONFIG_RTE_LIBRTE_THUNDERX_NICVF_PMD=y
-CONFIG_RTE_LIBRTE_THUNDERX_NICVF_DEBUG_INIT=n
-CONFIG_RTE_LIBRTE_THUNDERX_NICVF_DEBUG_RX=n
-CONFIG_RTE_LIBRTE_THUNDERX_NICVF_DEBUG_TX=n
-CONFIG_RTE_LIBRTE_THUNDERX_NICVF_DEBUG_DRIVER=n
-CONFIG_RTE_LIBRTE_THUNDERX_NICVF_DEBUG_MBOX=n
diff --git a/doc/guides/nics/thunderx.rst b/doc/guides/nics/thunderx.rst
index 1314ee9..a95b701 100644
--- a/doc/guides/nics/thunderx.rst
+++ b/doc/guides/nics/thunderx.rst
@@ -77,9 +77,8 @@ Config File Options
 The following options can be modified in the ``config`` file.
 Please note that enabling debugging options may affect system performance.
 
-- ``CONFIG_RTE_LIBRTE_THUNDERX_NICVF_PMD`` (default ``n``)
+- ``CONFIG_RTE_LIBRTE_THUNDERX_NICVF_PMD`` (default ``y``)
 
-  By default it is enabled only for defconfig_arm64-thunderx-* config.
   Toggle compilation of the ``librte_pmd_thunderx_nicvf`` driver.
 
 - ``CONFIG_RTE_LIBRTE_THUNDERX_NICVF_DEBUG_INIT`` (default ``n``)
-- 
2.5.5

  parent reply	other threads:[~2017-03-12 14:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 15:39 [dpdk-dev] [PATCH 1/2] net/thunderx: fix build issues with 32bit target Jerin Jacob
2017-03-10 15:39 ` [dpdk-dev] [PATCH 2/2] config: enable the thunderx nicvf driver Jerin Jacob
2017-03-12 14:02 ` [dpdk-dev] [PATCH v2 1/3] net/thunderx: fix build issues with 32bit target Jerin Jacob
2017-03-12 14:02   ` [dpdk-dev] [PATCH v2 2/3] net/thunderx: fix build issues with FreeBSD target Jerin Jacob
2017-03-12 14:02   ` Jerin Jacob [this message]
2017-03-19 14:48   ` [dpdk-dev] [PATCH v3 1/3] net/thunderx: fix build issues with 32bit target Jerin Jacob
2017-03-19 14:48     ` [dpdk-dev] [PATCH v3 2/3] net/thunderx: fix build issues with FreeBSD target Jerin Jacob
2017-03-19 14:48     ` [dpdk-dev] [PATCH v3 3/3] config: enable the thunderx nicvf driver Jerin Jacob
2017-03-20 12:21       ` Ferruh Yigit
2017-03-20 12:21     ` [dpdk-dev] [PATCH v3 1/3] net/thunderx: fix build issues with 32bit target Ferruh Yigit
2017-03-15 16:32 ` [dpdk-dev] [PATCH 1/2] " Ferruh Yigit

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=1489327352-31938-3-git-send-email-jerin.jacob@caviumnetworks.com \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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).