[dpdk-users] Fwd: errors while working with dpdk cuckoo hash

Shirley Avishour shirley at imvisiontech.com
Mon Aug 21 13:38:01 CEST 2017


---------- Forwarded message ----------
From: Shirley Avishour <shirley at imvisiontech.com>
Date: Mon, Aug 21, 2017 at 2:37 PM
Subject: errors while working with dpdk cuckoo hash
To: dev at dpdk.org


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?

Thanks,
Shirley
-------------- next part --------------
test iteration 0: entry_misses 0, add_entry_fail 0, entry_hits 30000, entry_rm 78000, entry_add 78000
test iteration 1: entry_misses 0, add_entry_fail 0, entry_hits 30000, entry_rm 78000, entry_add 78000

ALREADY EXISTS (VT 27, SID 0, SSN 6606, UBIT 0) (DST 0xB5ABE6D5/64703, SRC 0xD5445A3E/7183) SIG 3111868123
NOT FOUND (VT 27, SID 0, SSN 6606, UBIT 0) (DST 0xB5ABE6D5/64703, SRC 0xD5445A3E/7183)

test iteration 2: entry_misses 1, add_entry_fail 0, entry_hits 30001, entry_rm 77999, entry_add 77999
test iteration 3: entry_misses 0, add_entry_fail 0, entry_hits 30000, entry_rm 78000, entry_add 78000
test iteration 4: entry_misses 0, add_entry_fail 0, entry_hits 30000, entry_rm 78000, entry_add 78000

ADD (VT 56, SID 0, SSN 4444, UBIT 1) (DST 0xB5ABE6D5/64703, SRC 0xD5445A3E/7183) SIG 777357509
NOT FOUND (VT 56, SID 0, SSN 4444, UBIT 1) (DST 0xB5ABE6D5/64703, SRC 0xD5445A3E/7183)

test iteration 5: entry_misses 1, add_entry_fail 0, entry_hits 30000, entry_rm 77999, entry_add 78000
test iteration 6: entry_misses 0, add_entry_fail 0, entry_hits 30000, entry_rm 78000, entry_add 78000
test iteration 7: entry_misses 0, add_entry_fail 0, entry_hits 30000, entry_rm 78000, entry_add 78000
test iteration 8: entry_misses 0, add_entry_fail 0, entry_hits 30000, entry_rm 78000, entry_add 78000
test iteration 9: entry_misses 0, add_entry_fail 0, entry_hits 30000, entry_rm 78000, entry_add 78000


============================================================================================================


test iteration 2:
(*) receiving an already exist message for the given key before inserting to the table.
ALREADY EXISTS (VT 27, SID 0, SSN 6606, UBIT 0) (DST 0xB5ABE6D5/64703, SRC 0xD5445A3E/7183) SIG 3111868123
(*) when later performing lookup I get a not found message..
NOT FOUND (VT 27, SID 0, SSN 6606, UBIT 0) (DST 0xB5ABE6D5/64703, SRC 0xD5445A3E/7183)


test iteration 5:
(*) entry insterted to the table and was not found when performing lookup:
ADD (VT 56, SID 0, SSN 4444, UBIT 1) (DST 0xB5ABE6D5/64703, SRC 0xD5445A3E/7183) SIG 777357509
NOT FOUND (VT 56, SID 0, SSN 4444, UBIT 1) (DST 0xB5ABE6D5/64703, SRC 0xD5445A3E/7183)



More information about the users mailing list