DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: "Yeddula, Avinash" <ayeddula@ciena.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [ 2nd try ] Lookup mechanim in DPDK HASH table.
Date: Fri, 14 Aug 2015 10:25:02 +0100	[thread overview]
Message-ID: <20150814092502.GA8916@bricha3-MOBL3> (raw)
In-Reply-To: <A1E50D8AD6310E47A6C10F075AEDC02203754638FD@ONWVEXCHMB01.ciena.com>

On Thu, Aug 13, 2015 at 05:37:21PM -0400, Yeddula, Avinash wrote:
> Any comments on this question ?
> 
> Thanks
> -Avinash
> 
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Yeddula, Avinash
> Sent: Wednesday, August 12, 2015 3:04 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Lookup mechanim in DPDK HASH table.
> 
> Hello All,
> 
> I'm using DPDK extendable hash tables. This question is with respect to the lookup aspect of the hash table.
> I see that there is just one "t->key_offset" that is pre-defined for the hash table. I also understand that the frame needs to carry the "lookup_key / keys" in the meta data.
> 
> Here is my question:  How to support more than one lookup with different keys on the same frame on the same table.
> Use case: Src mac  lookup and dst mac lookup on the same mac table.
> 
> Thanks
> -Avinash

Just to confirm: this is using the extensible bucket hash in the rte_table library of packet framework,
rather than the standalone rte_hash library, right?

/Bruce

  reply	other threads:[~2015-08-14  9:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13 21:37 Yeddula, Avinash
2015-08-14  9:25 ` Bruce Richardson [this message]
2015-08-14 16:28   ` Yeddula, Avinash
2015-08-17 14:00   ` Singh, Jasvinder
2015-08-17 16:35     ` Yeddula, Avinash
2015-08-17 18:06       ` Venkateswara Rao Thummala
2015-08-17 18:29         ` Bly, Mike
2015-08-18 10:34         ` Dumitrescu, Cristian
2015-08-17 18:13       ` Singh, Jasvinder
2015-08-18 10:34         ` Dumitrescu, Cristian
2015-08-18 10:32 ` 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=20150814092502.GA8916@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=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).