[dpdk-dev] [PATCH] __rte_hash_add_key_with_hash not releasing multiwriter_lock in failure paths

Signed-off-by: mstolarchuk --- lib/librte_hash/rte_cuckoo_hash.c | 13 + 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/lib/librte_hash/rte_cuckoo_hash.c b/lib/librte_hash/rte_cuckoo_hash.c index 645c0cf..37a8110 100644 --- a/lib/librte_hash/rte_cuckoo_hash.c +++ b

[dpdk-dev] [PATCH 1/7] Use an accessor for rte_hash_key

Improves consistency, allows identifcation of use-sites Signed-off-by: mstolarchuk --- lib/librte_hash/rte_cuckoo_hash.c | 64 +++ 1 file changed, 31 insertions(+), 33 deletions(-) diff --git a/lib/librte_hash/rte_cuckoo_hash.c b/lib/librte_hash

[dpdk-dev] [PATCH 2/7] rwlock not released when the key exists

Consisntly use a single exit path in the code, have th various return values set then call the exit path. --- lib/librte_hash/rte_cuckoo_hash.c | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/lib/librte_hash/rte_cuckoo_hash.c b/lib/librte_hash/rte_cuc

[dpdk-dev] [PATCH 6/6] static variable whouldn't be used to compute recursion level

unrelated threads are inserting into the hash, each of these threads treat this static as their own property. Signed-off-by: mstolarchuk --- lib/librte_hash/rte_cuckoo_hash.c | 21 +++-- 1 file changed, 15 insertions(+), 6 deletions(-) diff --git a/lib/librte_hash/rte_cuckoo_has

[dpdk-dev] [PATCH 5/6] rwlock not released when the key exists

Consisntly use a single exit path in the code, have the various return values set 'ret' then use the single exit path. Signed-off-by: mstolarchuk --- lib/librte_hash/rte_cuckoo_hash.c | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/lib/l