From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [RFC 0/3] hash: optimize compare logic
Date: Thu, 21 Aug 2025 13:35:07 -0700 [thread overview]
Message-ID: <20250821203646.133506-1-stephen@networkplumber.org> (raw)
Recent discussion around handling small keys motivated furthur
examination of the compare logic.
Stephen Hemminger (3):
hash: move table of hash compare functions out of header
hash: reduce architecture special cases
hash: add support for common small key sizes
lib/hash/rte_cmp_arm64.h | 52 ----------
lib/hash/rte_cmp_x86.h | 56 +----------
lib/hash/rte_cuckoo_hash.c | 194 +++++++++++++++++++++++++++++++++++--
lib/hash/rte_cuckoo_hash.h | 79 +--------------
4 files changed, 187 insertions(+), 194 deletions(-)
--
2.47.2
next reply other threads:[~2025-08-21 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 20:35 Stephen Hemminger [this message]
2025-08-21 20:35 ` [RFC 1/3] hash: move table of hash compare functions out of header Stephen Hemminger
2025-08-21 20:35 ` [RFC 2/3] hash: reduce architecture special cases Stephen Hemminger
2025-08-21 20:35 ` [RFC 3/3] hash: add support for common small key sizes Stephen Hemminger
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=20250821203646.133506-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--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).