From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 1FBC68E5C for ; Mon, 17 Aug 2015 20:13:45 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga103.jf.intel.com with ESMTP; 17 Aug 2015 11:13:45 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,696,1432623600"; d="scan'208";a="750304874" Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by orsmga001.jf.intel.com with ESMTP; 17 Aug 2015 11:13:44 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.149]) by IRSMSX108.ger.corp.intel.com ([169.254.11.22]) with mapi id 14.03.0224.002; Mon, 17 Aug 2015 19:13:43 +0100 From: "Singh, Jasvinder" To: "Yeddula, Avinash" , "Richardson, Bruce" Thread-Topic: [dpdk-dev] [ 2nd try ] Lookup mechanim in DPDK HASH table. Thread-Index: AdDWEC6OvyssoEwzRkW/rjWnlKZeIQAWoiAAAKCu8WAABs0O8AADVACA Date: Mon, 17 Aug 2015 18:13:42 +0000 Message-ID: <54CBAA185211B4429112C315DA58FF6DD266EF@IRSMSX103.ger.corp.intel.com> References: <20150814092502.GA8916@bricha3-MOBL3> <54CBAA185211B4429112C315DA58FF6DD265C4@IRSMSX103.ger.corp.intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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:13:46 -0000 Hi, > -----Original Message----- > From: Yeddula, Avinash [mailto:ayeddula@ciena.com] > Sent: Monday, August 17, 2015 5:35 PM > To: Singh, Jasvinder; Richardson, Bruce > Cc: dev@dpdk.org; Bly, Mike > Subject: RE: [dpdk-dev] [ 2nd try ] Lookup mechanim in DPDK HASH table. >=20 > + Mike ( My team mate) > Hi Jasvinder, It's not a bidirectional packet flow. The pipeline looks so= mething > like this. >=20 > Ingress port-----Table 1 ----Table-2 ----- Mac_Table ----- Table4 ---- Eg= ress > port. >=20 > 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). >=20 > 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) >=20 There is as such no mechanism to support double lookup on the same table fo= r the packet. However, alternative approach could be- first perform dest= ination lookup and invoke action handler ( in both table hit & miss case).= In action handler, Src MAC + bridge ID key can be added to the table (rte_= pipeline_table_entry_add) . If a new entry is successfully added to the ha= sh for the specified key, or there is already an entry in the hash for the = specified key, then the position of the entry is returned. In this way, tab= le entries will be updated with incoming packets. =20 > Thanks > -Avinash >=20 > -----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. >=20 >=20 >=20 > > -----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 >=20 > Could you share detail on the two different keys used for lookups. In cas= e 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 >=20 > Jasvinder