From: Stephen Hemminger <stephen@networkplumber.org>
To: Bing Zhao <bingz@mellanox.com>
Cc: orika@mellanox.com, viacheslavo@mellanox.com,
rasland@mellanox.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: introduce mlx5 hash list
Date: Tue, 5 Nov 2019 09:20:59 -0800 [thread overview]
Message-ID: <20191105092059.25770f57@hermes.lan> (raw)
In-Reply-To: <1572967680-93338-1-git-send-email-bingz@mellanox.com>
On Tue, 5 Nov 2019 17:28:00 +0200
Bing Zhao <bingz@mellanox.com> wrote:
> Introduce simple hash list to the mlx5 utilities. User can define
> its own data structure containing the mlx5_hlist_entry and create
> the hash list table via the creation interface. Then the entry will
> be inserted into the table and linked to the corresponding list
> head. User should guarantee there is no collision of the key and
> provide a callback function to handle all the remaining entries in
> the table when destroying the hash list. User should define a proper
> number of the list heads in the table in order to get a better
> performance. The LSB of the 'key' is used to calculate the index of
> the head in the list heads array.
> This implementation is not multi-threads safe right now.
>
> Signed-off-by: Bing Zhao <bingz@mellanox.com>
There is already a plethora of hash routines in DPDK, why introduce
a chained hash list like Linux kernel?
next prev parent reply other threads:[~2019-11-05 17:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 15:28 [dpdk-dev] [PATCH] net/mlx5: introduce mlx5 hash list Bing Zhao
2019-11-05 15:29 ` Slava Ovsiienko
2019-11-05 16:02 ` Raslan Darawsheh
2019-11-05 17:26 ` Stephen Hemminger
2019-11-06 8:14 ` Raslan Darawsheh
2019-11-05 17:20 ` Stephen Hemminger [this message]
2019-11-05 18:49 ` Slava Ovsiienko
2019-11-05 17:25 ` Stephen Hemminger
2019-11-06 7:45 ` Bing Zhao
2019-11-06 13:07 ` [dpdk-dev] [PATCH v2] " Bing Zhao
2019-11-07 9:20 ` Bing Zhao
2019-11-07 22:46 ` Raslan Darawsheh
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=20191105092059.25770f57@hermes.lan \
--to=stephen@networkplumber.org \
--cc=bingz@mellanox.com \
--cc=dev@dpdk.org \
--cc=orika@mellanox.com \
--cc=rasland@mellanox.com \
--cc=viacheslavo@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.