From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-f169.google.com (mail-ig0-f169.google.com [209.85.213.169]) by dpdk.org (Postfix) with ESMTP id 6DBCD8D92 for ; Mon, 17 Aug 2015 20:06:29 +0200 (CEST) Received: by igbjg10 with SMTP id jg10so61941145igb.0 for ; Mon, 17 Aug 2015 11:06:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JVBezhBtjU7FhtjxpktoLG7Xchma1jYGQEPJuqbncq8=; b=Ay/guDykF/YTnMpJF+CuiqrZ1ZjutqeJmwI2AWC6LHiQpbkTQZ2MS+xUQlYwXhJ0lk V7GQKQdDsBUwcqZWZ92CcaJoyIOPfS8CkktJ4NmGiFZ6dOuOfAgaMc+ngT158TGIufZ1 uGUXH/RlNNvmBbgrTOzoWynAdRcw7OEPwvrSm7MxTwEyl2vSOZA+Ud8ykCR6xe4KEo+o 0YJmcW+eZ5qI/MVtxxHtS0+mYZbfBgz9O255YZEBxmR/2rsPhUf9N4k37wiHTZPqjsar gGsxwixfuN1NsZfJ6kuYv9oCWG1JKLJpD/B+hjpOKm6Jf5xb4Lky3owwn98JfaL0Ct9l f5zQ== MIME-Version: 1.0 X-Received: by 10.50.253.36 with SMTP id zx4mr18207460igc.43.1439834788641; Mon, 17 Aug 2015 11:06:28 -0700 (PDT) Received: by 10.107.56.194 with HTTP; Mon, 17 Aug 2015 11:06:28 -0700 (PDT) In-Reply-To: References: <20150814092502.GA8916@bricha3-MOBL3> <54CBAA185211B4429112C315DA58FF6DD265C4@IRSMSX103.ger.corp.intel.com> Date: Mon, 17 Aug 2015 23:36:28 +0530 Message-ID: From: Venkateswara Rao Thummala To: "Yeddula, Avinash" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" , "Bly, Mike" Subject: Re: [dpdk-dev] [ 2nd try ] Lookup mechanim in DPDK HASH table. X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2015 18:06:29 -0000 Hi Avinash, I think, you can use the same table by just updating the packet meta data based on the Look UP. In the first lookup, you can populate the meta data [key offset] with the source MAC and in the second lookup, you can populate the same meta data with the destination lookup. I think this should work. Thanks Venkat OneHop Networks On 17 August 2015 at 22:05, Yeddula, Avinash wrote: > + Mike ( My team mate) > Hi Jasvinder, It's not a bidirectional packet flow. The pipeline looks > something like this. > > Ingress port-----Table 1 ----Table-2 ----- Mac_Table ----- Table4 ---- > Egress port. > > Before the frame goes reaches table 4, we do 2 lookups at the mac table. > 1. src lookup ( To learn the MAC on the bridge) > 2. dst lookup ( Flooding if dst MAC look up fails else Unicast/forward if > dst lookup success). > > Here are the keys we are using. > Src lookup key - Src MAC (src MAC in the frame) + Bridge ID ( Bridge on > which it arrived). > Dst lookup key - Dst MAC (dst MAC in the frame) + Bridge ID ( Bridge on > which it arrived) > > > Thanks > -Avinash > > -----Original Message----- > From: Singh, Jasvinder [mailto:jasvinder.singh@intel.com] > Sent: Monday, August 17, 2015 7:00 AM > To: Richardson, Bruce; Yeddula, Avinash > Cc: dev@dpdk.org > Subject: RE: [dpdk-dev] [ 2nd try ] Lookup mechanim in DPDK HASH table. > > > > > -----Original Message----- > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bruce Richardson > > Sent: Friday, August 14, 2015 10:25 AM > > To: Yeddula, Avinash > > Cc: dev@dpdk.org > > Subject: Re: [dpdk-dev] [ 2nd try ] Lookup mechanim in DPDK HASH table. > > > > 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 > > Could you share detail on the two different keys used for lookups. In case > if you are considering bidirectional packet flow between the source and > destination, symmetric hash can be used- > http://www.ndsl.kaist.edu/~kyoungsoo/papers/TR-symRSS.pdf > > Jasvinder >