DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ashwin Sekhar T K <ashwin.sekhar@caviumnetworks.com>
To: thomas@monjalon.net, jasvinder.singh@intel.com,
	viktorin@rehivetech.com, jerin.jacob@caviumnetworks.com,
	jianbo.liu@linaro.org
Cc: dev@dpdk.org, Ashwin Sekhar T K <ashwin.sekhar@caviumnetworks.com>
Subject: [dpdk-dev] [PATCH 2/2] test: add tests for arm64 CRC neon versions
Date: Thu, 27 Apr 2017 07:10:21 -0700	[thread overview]
Message-ID: <20170427141021.18767-2-ashwin.sekhar@caviumnetworks.com> (raw)
In-Reply-To: <20170427141021.18767-1-ashwin.sekhar@caviumnetworks.com>

Verified the changes with crc_autotest unit test case

Signed-off-by: Ashwin Sekhar T K <ashwin.sekhar@caviumnetworks.com>
---
 test/test/test_crc.c | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/test/test/test_crc.c b/test/test/test_crc.c
index cd5af69..ac0e359 100644
--- a/test/test/test_crc.c
+++ b/test/test/test_crc.c
@@ -178,6 +178,15 @@ test_crc(void)
 		return ret;
 	}
 
+	/* set CRC neon mode */
+	rte_net_crc_set_alg(RTE_NET_CRC_NEON);
+
+	ret = test_crc_calc();
+	if (ret < 0) {
+		printf("test_crc (arm64 neon pmull): failed (%d)\n", ret);
+		return ret;
+	}
+
 	return 0;
 }
 
-- 
2.7.4

  reply	other threads:[~2017-04-27 14:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27 14:10 [dpdk-dev] [PATCH 1/2] net: add arm64 neon version of CRC compute APIs Ashwin Sekhar T K
2017-04-27 14:10 ` Ashwin Sekhar T K [this message]
2017-04-28  9:34 ` [dpdk-dev] [PATCH v2 " Ashwin Sekhar T K
2017-04-28  9:34   ` [dpdk-dev] [PATCH v2 2/2] test: add tests for arm64 CRC neon versions Ashwin Sekhar T K
2017-04-28  9:55 ` [dpdk-dev] [PATCH 1/2] net: add arm64 neon version of CRC compute APIs Jan Viktorin
2017-04-28 10:19   ` Sekhar, Ashwin
2017-05-03 16:58     ` Jan Viktorin

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=20170427141021.18767-2-ashwin.sekhar@caviumnetworks.com \
    --to=ashwin.sekhar@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=jasvinder.singh@intel.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=jianbo.liu@linaro.org \
    --cc=thomas@monjalon.net \
    --cc=viktorin@rehivetech.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).