DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gowrishankar Muthukrishnan <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 <gowrishankar.m@linux.vnet.ibm.com>
Subject: [dpdk-dev] [PATCH v4 6/6] l3fwd: add altivec support for em_hash_key
Date: Sat,  6 Aug 2016 18:02:45 +0530	[thread overview]
Message-ID: <1470486765-2672-7-git-send-email-gowrishankar.m@linux.vnet.ibm.com> (raw)
In-Reply-To: <1470486765-2672-1-git-send-email-gowrishankar.m@linux.vnet.ibm.com>

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

This patch adds ppc64le port for em_mask_key function.

Signed-off-by: Gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
---
 examples/l3fwd/l3fwd_em.c | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/examples/l3fwd/l3fwd_em.c b/examples/l3fwd/l3fwd_em.c
index def5a02..6053a62 100644
--- a/examples/l3fwd/l3fwd_em.c
+++ b/examples/l3fwd/l3fwd_em.c
@@ -259,8 +259,16 @@ em_mask_key(void *key, xmm_t mask)
 
 	return vandq_s32(data, mask);
 }
+#elif defined(RTE_MACHINE_CPUFLAG_ALTIVEC)
+static inline xmm_t
+em_mask_key(void *key, xmm_t mask)
+{
+	xmm_t data = vec_ld(0, (xmm_t *)(key));
+
+	return vec_and(data, mask);
+}
 #else
-#error No vector engine (SSE, NEON) available, check your toolchain
+#error No vector engine (SSE, NEON, ALTIVEC) available, check your toolchain
 #endif
 
 static inline uint8_t
-- 
1.9.1

      parent reply	other threads:[~2016-08-06 12:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-06 12:32 [dpdk-dev] [PATCH v4 0/6] enable lpm, acl and other missing libraries in ppc64le Gowrishankar Muthukrishnan
2016-08-06 12:32 ` [dpdk-dev] [PATCH v4 1/6] lpm: add altivec intrinsics for dpdk lpm on ppc_64 Gowrishankar Muthukrishnan
2016-08-06 12:32 ` [dpdk-dev] [PATCH v4 2/6] acl: add altivec intrinsics for dpdk acl " Gowrishankar Muthukrishnan
2016-08-06 12:32 ` [dpdk-dev] [PATCH v4 3/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64 Gowrishankar Muthukrishnan
2016-08-09  9:07   ` Chao Zhu
2016-08-09 11:13     ` gowrishankar muthukrishnan
2016-08-11 10:29       ` Chao Zhu
2016-08-11 12:01         ` gowrishankar muthukrishnan
2016-08-12  8:44           ` Chao Zhu
2016-08-12  8:59             ` gowrishankar muthukrishnan
2016-08-12 10:15               ` Chao Zhu
2016-08-12 10:34                 ` gowrishankar muthukrishnan
2016-08-12 12:05                 ` gowrishankar muthukrishnan
2016-08-06 12:32 ` [dpdk-dev] [PATCH v4 4/6] table: cache align rte_bucket_4_8 Gowrishankar Muthukrishnan
2016-08-06 12:32 ` [dpdk-dev] [PATCH v4 5/6] sched: enable sched library for ppc64le Gowrishankar Muthukrishnan
2016-08-06 12:32 ` Gowrishankar Muthukrishnan [this message]

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=1470486765-2672-7-git-send-email-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).