DPDK usage discussions
 help / color / mirror / Atom feed
From: Syam Prasad N Pearson <syam.pearson@gadgeon.com>
To: users@dpdk.org, dev@dpdk.org
Cc: Syam Prasad N Pearson <syam.pearson@gadgeon.com>
Subject: Doubt regarding DPDK hash Library implementation
Date: Mon, 1 Nov 2021 16:25:32 +0530	[thread overview]
Message-ID: <CAA2VcQjJPvz63p=gzM+Sh4J7UCRSUaHg5NBgB0o-pmq3m=kmmg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

Dear Sir/Madam,
I am a developer trying to get familiar with the DPDK hash library. I tried
to make and use a hash table successfully.
During the development I came across a variable

/** Number of items per bucket. */
*#define RTE_HASH_BUCKET_ENTRIES 8*

defined inside:
dpdk-20.11.3/dpdk-stable-20.11.3/lib/librte_hash /rte_cuckoo_hash.h

Why does the library take this value as *8*, is there any particular reason
for this? what if it is 16,32... etc.

I am using DPDK 20.11.3 LTS.

Please help.

-- 
Regards,
Syam Pearson
Syam Pearson
Gadgeon Smart Systems
m: +91-97460-44420 (India)
w: www.gadgeon.com
<https://link.aeusercontent.com/mt/lt/D78C05ADDA56BE856A051569556899538/1?targetURL=https%3A%2F%2Fwww.gadgeon.com%2F>
www.delpheon.io
<https://link.aeusercontent.com/mt/lt/D78C05ADDA56BE856A051569556899538/2?targetURL=https%3A%2F%2Fdelpheon.io%2F>

<https://twitter.com/gadgeon>  [image:
www.linkedin.com/in/kirankumar-c-32349964]
<http://www.linkedin.com/in/syam-prasad-n-pearson-4903b5a8>

[-- Attachment #2: Type: text/html, Size: 7020 bytes --]

             reply	other threads:[~2021-11-04 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 10:55 Syam Prasad N Pearson [this message]
2021-11-04 14:11 ` [dpdk-dev] " Thomas Monjalon
2021-11-04 14:46   ` Kinsella, Ray
2021-11-04 16:39     ` Medvedkin, Vladimir
2021-11-04 16:49       ` Thomas Monjalon
2021-11-06 23:23         ` Syam Prasad N Pearson

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='CAA2VcQjJPvz63p=gzM+Sh4J7UCRSUaHg5NBgB0o-pmq3m=kmmg@mail.gmail.com' \
    --to=syam.pearson@gadgeon.com \
    --cc=dev@dpdk.org \
    --cc=users@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).