From: "Yeddula, Avinash" <ayeddula@ciena.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Need your thoughts on DPDK hash table / DPDK lookup/insert API's
Date: Fri, 25 Sep 2015 18:26:40 -0400 [thread overview]
Message-ID: <A1E50D8AD6310E47A6C10F075AEDC0220379FB2A6D@ONWVEXCHMB01.ciena.com> (raw)
Hello All,
1. I've a scenario where I need to walk the entire Hash table to retrieve the data. I'm currently using DPDK extensible bucket hash in the rte_table library of packet framework.
Since I'll not be storing the keys anywhere else, I don't have a way to walk hash table.
I'm planning to write one for my application, but just wanted to check with the DPDK community on their thoughts.
2. I have a scenario where the components whose are not part of the pipeline needs to call the DPDK lookup/add apis. Moreover they are interested in lookup/insert one entry at a time. With the current approach, I know everything works in bursts to achieve more/better performance.
Currently a lookup api's looks like this.
static int rte_table_array_lookup( void *table, struct rte_mbuf **pkts, uint64_t pkts_mask, uint64_t *lookup_hit_mask, void **entries)
New addition to the existing lookup, I would like it to be something like this (not exactly, something similar). With this the outside guy doesn't have to construct "rte_mbuf and put the key in the metadata for the DPDK lookup API to act "
static int rte_table_array_single_pkt_lookup( void *table, void *key, void *entry)
Any thoughts on adding these 2 items officially to dpdk library.
Thanks
-Avinash
next reply other threads:[~2015-09-25 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 22:26 Yeddula, Avinash [this message]
2015-09-28 20:46 ` Dumitrescu, Cristian
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=A1E50D8AD6310E47A6C10F075AEDC0220379FB2A6D@ONWVEXCHMB01.ciena.com \
--to=ayeddula@ciena.com \
--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 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).