From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Shirley Avishour <shirley@imvisiontech.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] errors while working with dpdk cuckoo hash
Date: Wed, 30 Aug 2017 12:37:06 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC11079@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CACn717j+iKUFTiCZjfBakLvwLOACtYHMsBMM6AP8p9+yri5mXg@mail.gmail.com>
Hi Shirley,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Shirley Avishour
> Sent: Monday, August 21, 2017 12:37 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] errors while working with dpdk cuckoo hash
>
> Hi,
>
> I am running an application over dpdk ver 16.04.
> My application massively inserting and deleting from a hash table using a
> key that can be very similar for many instances.
> I noticed that in some cases I am unable to find an entry while I am certain
> it was inserted successfully.
> I wrote a test to try and reproduce the problem and I have managed to
> recreate the problem.
> Attached is a c file containing the test which recreates the problem.
> The key and hash function/hash size which I used in the test are identical to
> what I use in my application.
> attached is also a file containing the printouts of the test and indication to 2
> of the problems I encountered.
> Are these known issues? is there a fix for that?
Could you attach the code? I only see the results, but not the C code.
Thanks,
Pablo
>
> Thanks,
> Shirley
next prev parent reply other threads:[~2017-08-30 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 11:37 Shirley Avishour
2017-08-30 12:37 ` De Lara Guarch, Pablo [this message]
2017-08-30 12:40 ` Shirley Avishour
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=E115CCD9D858EF4F90C690B0DCB4D8976CC11079@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=shirley@imvisiontech.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).