DPDK usage discussions
 help / color / mirror / Atom feed
From: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: rte_hash_table lookup failed
Date: Fri, 14 Apr 2023 06:15:56 +0000	[thread overview]
Message-ID: <PSAPR04MB5516D31EAFB69B06625CF81AD6999@PSAPR04MB5516.apcprd04.prod.outlook.com> (raw)

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

Hi All,
   Need inputs on using rte_hash_table.
Created hash table to store the mbuf as data and the key is sequence number.
Hashtable size is 8096 I have stored the 200packets which was received.
There is no error in during insert.
While I am trying to do lookup using loop (rte_hash_lookup_data) it is only working for first 63 entries .
For 64th time lookup failed to return data for the given key.
This is happen exactly for the 64th entry not for the particular key value .
Whatever keys stored after 63rd I am not able fetch using rte_hash_lookup_data.

If I do the rte_hash_iterate() , I able to get the all the entries stored in the hash table.
Could any please tell me why the lookup not returning data even though the data and key is present in the table.


Hash table details:
#define MAX_INNER_ENTRIES 8096
mempool MEMPOOL3 buffer 2304 pool 4096k cache 128 cpu 0 (create using command line)

struct rte_hash_parameters mbuf_hash_params = {
        .name = NULL,
        .entries = MAX_INNER_ENTRIES,
        .key_len = sizeof(uint32_t),
        .hash_func = rte_hash_crc,
        .hash_func_init_val = 0,
        .extra_flag = RTE_HASH_EXTRA_FLAGS_MULTI_WRITER_ADD | RTE_HASH_EXTRA_FLAGS_RW_CONCURRENCY,
};


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

                 reply	other threads:[~2023-04-14  6:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=PSAPR04MB5516D31EAFB69B06625CF81AD6999@PSAPR04MB5516.apcprd04.prod.outlook.com \
    --to=balakrishnan.k1@tatacommunications.com \
    --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).