From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Yipeng Wang <yipeng1.wang@intel.com>,
Sameh Gobriel <sameh.gobriel@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Subject: Re: [PATCH v4 0/4] Cuckoo hash optimization for small sizes
Date: Thu, 23 Oct 2025 20:52:36 +0200 [thread overview]
Message-ID: <2964145.MzOyzyC30C@thomas> (raw)
In-Reply-To: <20250916150219.104936-1-stephen@networkplumber.org>
16/09/2025 17:00, Stephen Hemminger:
> Recent discussion around handling small keys motivated furthur
> examination of the compare logic.
>
> v4 - add test for more sizes, and a few more special case sizes.
>
> Stephen Hemminger (4):
> hash: move table of hash compare functions out of header
> hash: use static_assert
> hash: reduce architecture special cases
> hash: add support for common small key sizes
I really would like to see a review from the hash lib maintainers.
We need at least some design and performance considerations.
Cc Yipeng, Sameh, Bruce and Vladimir
prev parent reply other threads:[~2025-10-23 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0250818233102.180207-1-stephen@networkplumber.org>
2025-09-16 15:00 ` Stephen Hemminger
2025-09-16 15:00 ` [PATCH v4 1/4] hash: move table of hash compare functions out of header Stephen Hemminger
2025-09-16 15:00 ` [PATCH v4 2/4] hash: use static_assert Stephen Hemminger
2025-09-16 15:00 ` [PATCH v4 3/4] hash: reduce architecture special cases Stephen Hemminger
2025-10-27 18:16 ` Wathsala Vithanage
2025-09-16 15:00 ` [PATCH v4 4/4] hash: add support for common small key sizes Stephen Hemminger
2025-10-23 18:52 ` Thomas Monjalon [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=2964145.MzOyzyC30C@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=sameh.gobriel@intel.com \
--cc=stephen@networkplumber.org \
--cc=vladimir.medvedkin@intel.com \
--cc=yipeng1.wang@intel.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).