From: Nipun Gupta <nipun.gupta@nxp.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, david.marchand@redhat.com,
hemant.agrawal@nxp.com, sachin.saxena@nxp.com,
Nipun Gupta <nipun.gupta@nxp.com>
Subject: [dpdk-dev] [PATCH v2] config: disable 1588 timer support on DPAA2
Date: Thu, 31 Oct 2019 18:18:35 +0530 [thread overview]
Message-ID: <20191031124835.29927-1-nipun.gupta@nxp.com> (raw)
In-Reply-To: <20191004111106.30267-1-nipun.gupta@nxp.com>
This patch disables the 1588 timer support by default on DPAA2
platform due to the performance impact.
By default it is disabled in the common/base, so remove the entry
from DPAA2.
Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
---
Changes in v2:
- Change only the 1588 timestamp option in DPAA2 and do not touch
the CONFIG_RTE_LIBRTE_DPAA2_USE_PHYS_IOVA option.
config/defconfig_arm64-dpaa2-linuxapp-gcc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/config/defconfig_arm64-dpaa2-linuxapp-gcc b/config/defconfig_arm64-dpaa2-linuxapp-gcc
index 5c7eddd5e..b2ccbec0c 100644
--- a/config/defconfig_arm64-dpaa2-linuxapp-gcc
+++ b/config/defconfig_arm64-dpaa2-linuxapp-gcc
@@ -15,8 +15,8 @@ CONFIG_RTE_CACHE_LINE_SIZE=64
CONFIG_RTE_PKTMBUF_HEADROOM=128
-# Enable IEEE1588, Keep it disable by default
-CONFIG_RTE_LIBRTE_IEEE1588=y
+# Disable IEEE1588 by default
+CONFIG_RTE_LIBRTE_IEEE1588=n
# Doesn't support NUMA
CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=n
--
2.17.1
next prev parent reply other threads:[~2019-10-31 13:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 11:11 [dpdk-dev] [PATCH] config: disable iova phys for dpaa and 1588 for dpaa2 Nipun Gupta
2019-10-10 12:26 ` Hemant Agrawal
2019-10-27 11:03 ` David Marchand
2019-10-30 9:36 ` Nipun Gupta
2019-10-30 10:14 ` David Marchand
2019-10-31 6:56 ` Nipun Gupta
2019-10-31 12:48 ` Nipun Gupta [this message]
2019-10-31 16:18 ` [dpdk-dev] [PATCH v2] config: disable 1588 timer support on DPAA2 David Marchand
2019-11-01 2:52 ` Hemant Agrawal
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=20191031124835.29927-1-nipun.gupta@nxp.com \
--to=nipun.gupta@nxp.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=sachin.saxena@nxp.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 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).