From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 78] Mismatch between return value and documentation for `rte_hash_lookup_data` (cuckoo hashing implementation)
Date: Mon, 06 Aug 2018 16:49:21 +0000 [thread overview]
Message-ID: <bug-78-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=78
Bug ID: 78
Summary: Mismatch between return value and documentation for
`rte_hash_lookup_data` (cuckoo hashing implementation)
Product: DPDK
Version: 18.05
Hardware: All
OS: All
Status: CONFIRMED
Severity: minor
Priority: Normal
Component: doc
Assignee: dev@dpdk.org
Reporter: t-pehous@microsoft.com
Target Milestone: ---
Documentation for `rte_hash_lookup_data` specifies that this method returns 0
on successful data lookup or positive error code on not-found / wrong
parameters. In reality it returns positive index of found data on success and
negative error on error, in essence it behaves the same as (i.e. the same as
rte_hash_lookup while also (correctly) populating the data pointer).
rte_cuckoo_hash.c: 733
```c
int
rte_hash_lookup_data(const struct rte_hash *h, const void *key, void **data) {
RETURN_IF_TRUE(((h == NULL) || (key == NULL)), -EINVAL);
return __rte_hash_lookup_with_hash(h, key, rte_hash_hash(h,
key), data); } ```
Rte_cuckoo_hash.c: 693
```c
static inline int32_t
__rte_hash_lookup_with_hash(const struct rte_hash *h, const void *key,
hash_sig_t sig, void **data) {
...
/*
* Return index
where key is stored,
* subtracting
the first dummy index
*/
return
bkt->key_idx[i] - 1; ```
DPDK version 18.05 release.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2018-08-06 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 16:49 bugzilla [this message]
2018-08-07 17:34 ` [Bug 78] Mismatch between return value and documentation for `rte_hash_lookup_data` (cuckoo hashing implementation) bugzilla
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=bug-78-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.