DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
To: dev@dpdk.org
Cc: Chao Zhu <chaozhu@linux.vnet.ibm.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Konstantin Ananyev <konstantin.ananyev@intel.com>,
	Thomas Monjalon <thomas.monjalon@6wind.com>,
	Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
	Pradeep <pradeep@us.ibm.com>,
	Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
Subject: [dpdk-dev] [PATCH v7 4/9] table: enable table library for ppc64le
Date: Thu,  8 Sep 2016 22:18:06 +0530	[thread overview]
Message-ID: <5e1a78a8eab5f8efae6037abf3a67146e5c8d6f4.1473349652.git.gowrishankar.m@linux.vnet.ibm.com> (raw)
In-Reply-To: <cover.1473349652.git.gowrishankar.m@linux.vnet.ibm.com>
In-Reply-To: <cover.1473349652.git.gowrishankar.m@linux.vnet.ibm.com>

From: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>

This patch enables librte_table in ppc64le.

Signed-off-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
Acked-by: Chao Zhu <chaozhu@linux.vnet.ibm.com>
---
 config/defconfig_ppc_64-power8-linuxapp-gcc | 1 -
 1 file changed, 1 deletion(-)

diff --git a/config/defconfig_ppc_64-power8-linuxapp-gcc b/config/defconfig_ppc_64-power8-linuxapp-gcc
index dede34f..41f67d5 100644
--- a/config/defconfig_ppc_64-power8-linuxapp-gcc
+++ b/config/defconfig_ppc_64-power8-linuxapp-gcc
@@ -59,5 +59,4 @@ CONFIG_RTE_LIBRTE_FM10K_PMD=n
 # This following libraries are not available on Power. So they're turned off.
 CONFIG_RTE_LIBRTE_SCHED=n
 CONFIG_RTE_LIBRTE_PORT=n
-CONFIG_RTE_LIBRTE_TABLE=n
 CONFIG_RTE_LIBRTE_PIPELINE=n
-- 
1.9.1

  parent reply	other threads:[~2016-09-08 16:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 16:48 [dpdk-dev] [PATCH v7 0/9] enable lpm, acl and other missing libraries in ppc64le Gowrishankar
2016-09-08 16:48 ` [dpdk-dev] [PATCH v7 1/9] lpm: add altivec intrinsics for dpdk lpm on ppc_64 Gowrishankar
2016-09-08 16:48 ` [dpdk-dev] [PATCH v7 2/9] acl: add altivec intrinsics for dpdk acl " Gowrishankar
2016-09-08 16:48 ` [dpdk-dev] [PATCH v7 3/9] l3fwd: add altivec support for em_hash_key Gowrishankar
2016-09-08 16:48 ` Gowrishankar [this message]
2016-09-08 16:48 ` [dpdk-dev] [PATCH v7 5/9] sched: enable sched library for ppc64le Gowrishankar
2016-09-08 16:48 ` [dpdk-dev] [PATCH v7 6/9] port: enable port " Gowrishankar
2016-09-08 16:48 ` [dpdk-dev] [PATCH v7 7/9] pipeline: enable pipeline " Gowrishankar
2016-09-08 16:48 ` [dpdk-dev] [PATCH v7 8/9] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64 Gowrishankar
2016-09-08 16:48 ` [dpdk-dev] [PATCH v7 9/9] table: fix verification on hash bucket header alignment Gowrishankar
2016-09-08 16:54 ` [dpdk-dev] [PATCH v7 0/9] enable lpm, acl and other missing libraries in ppc64le Dumitrescu, Cristian
2016-09-09 15:59   ` Thomas Monjalon
2016-09-27  6:46     ` gowrishankar muthukrishnan
2016-09-27  7:01       ` [dpdk-dev] [dpdk-stable] " Yuanhan Liu

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=5e1a78a8eab5f8efae6037abf3a67146e5c8d6f4.1473349652.git.gowrishankar.m@linux.vnet.ibm.com \
    --to=gowrishankar.m@linux.vnet.ibm.com \
    --cc=bruce.richardson@intel.com \
    --cc=chaozhu@linux.vnet.ibm.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=pradeep@us.ibm.com \
    --cc=thomas.monjalon@6wind.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).