DPDK patches and discussions
 help / color / mirror / Atom feed
From: Harjot Singh <Harjot.Singh@arm.com>
Cc: dev@dpdk.org, nd@arm.com, Harjot Singh <Harjot.Singh@arm.com>
Subject: [PATCH 0/1] hash: add SVE support for bulk key lookup
Date: Thu, 17 Aug 2023 21:24:16 +0000	[thread overview]
Message-ID: <20230817212417.3637080-1-Harjot.Singh@arm.com> (raw)

- Add SVE code to compare_signatures().
- Tested on Aarch64 N2 based platform with 128 bit vector registers. 

Performance Numbers from hash_perf_autotest :

Elements in Primary or Secondary Location

Results (in CPU cycles/operation)
-----------------------------------
 Operations without data

Without pre-computed hash values

Keysize     Add/Lookup/Lookup_bulk
            Neon         SVE
4           93/71/26     93/71/27
8           93/70/26     93/70/27
9           94/74/27     94/74/28
13          100/80/31    100/79/32
16          100/78/30    100/78/31
32          109/110/38   108/110/39

With pre-computed hash values

Keysize     Add/Lookup/Lookup_bulk
            Neon         SVE
4           83/58/27     83/58/29
8           83/57/27     83/57/28
9           83/60/28     83/60/29
13          84/60/28     83/60/29
16          83/58/27     83/58/29
32          84/68/31     84/68/32

Note: Functionality verified with 256 bit vector length platform.

Harjot Singh (1):
  hash: add SVE support for bulk key lookup

 .mailmap                   |  1 +
 lib/hash/rte_cuckoo_hash.c | 37 ++++++++++++++++++++++++++++++++++++-
 lib/hash/rte_cuckoo_hash.h |  1 +
 3 files changed, 38 insertions(+), 1 deletion(-)

-- 
2.25.1


             reply	other threads:[~2023-08-17 21:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 21:24 Harjot Singh [this message]
2023-08-17 21:24 ` [PATCH 1/1] " Harjot Singh
2023-09-29 15:36   ` David Marchand

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=20230817212417.3637080-1-Harjot.Singh@arm.com \
    --to=harjot.singh@arm.com \
    --cc=dev@dpdk.org \
    --cc=nd@arm.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).