DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH 0/4] optimize and use armv8 CRC extensions for hash library
Date: Tue, 24 Nov 2015 00:15:34 +0530	[thread overview]
Message-ID: <1448304338-22767-1-git-send-email-jerin.jacob@caviumnetworks.com> (raw)

- This patch set has the changes required for optimised hash library usage in arm64 perspective
- Tested on Juno and Thunderx boards
- Tested and verified the changes with following DPDK unit test cases
        hash_functions_autotest
        hash_autotest
        hash_perf_autotest
        hash_scaling_autotes
-   Created the new xgene1 machine target to address the difference
    in optional armv8-a CRC extension availability compared to
    default armv8-a machine target(enabled CRC extension by default)
-  Supersededs the [dpdk-dev] [PATCH] hash: replace libc memcmp with
 optimized memory compare functions for arm64 patch


Jerin Jacob (4):
  hash: replace libc memcmp with optimized memory compare functions for
    arm64
  hash: implement rte_hash_crc_* based on armv8-a CRC32 instructions
  hash: select hash function as CRC if armv8-a CRC extension available
  mk: add xgene1 machine target based on armv8-a

 app/test/test_hash.c                       |   7 ++
 config/defconfig_arm64-xgene1-linuxapp-gcc |  56 +++++++++++
 lib/librte_hash/Makefile                   |   3 +
 lib/librte_hash/rte_cmp_arm64.h            | 114 ++++++++++++++++++++++
 lib/librte_hash/rte_crc_arm64.h            | 151 +++++++++++++++++++++++++++++
 lib/librte_hash/rte_cuckoo_hash.c          |   9 +-
 lib/librte_hash/rte_fbk_hash.h             |   2 +-
 lib/librte_hash/rte_hash_crc.h             |   7 ++
 mk/machine/armv8a/rte.vars.mk              |   2 +-
 mk/machine/thunderx/rte.vars.mk            |   2 +-
 mk/machine/xgene1/rte.vars.mk              |  58 +++++++++++
 mk/rte.cpuflags.mk                         |   4 +
 mk/toolchain/gcc/rte.toolchain-compat.mk   |   6 +-
 13 files changed, 415 insertions(+), 6 deletions(-)
 create mode 100644 config/defconfig_arm64-xgene1-linuxapp-gcc
 create mode 100644 lib/librte_hash/rte_cmp_arm64.h
 create mode 100644 lib/librte_hash/rte_crc_arm64.h
 create mode 100644 mk/machine/xgene1/rte.vars.mk

-- 
2.1.0

             reply	other threads:[~2015-11-23 18:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 18:45 Jerin Jacob [this message]
2015-11-23 18:45 ` [dpdk-dev] [PATCH 1/4] hash: replace libc memcmp with optimized memory compare functions for arm64 Jerin Jacob
2015-11-23 18:45 ` [dpdk-dev] [PATCH 2/4] hash: implement rte_hash_crc_* based on armv8-a CRC32 instructions Jerin Jacob
2015-11-23 18:45 ` [dpdk-dev] [PATCH 3/4] hash: select hash function as CRC if armv8-a CRC extension available Jerin Jacob
2015-11-23 18:45 ` [dpdk-dev] [PATCH 4/4] mk: add xgene1 machine target based on armv8-a Jerin Jacob
2015-11-25 21:11 ` [dpdk-dev] [PATCH 0/4] optimize and use armv8 CRC extensions for hash library Thomas Monjalon

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=1448304338-22767-1-git-send-email-jerin.jacob@caviumnetworks.com \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    /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).