From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0b-00103a01.pphosted.com (mx0b-00103a01.pphosted.com [67.231.152.227]) by dpdk.org (Postfix) with ESMTP id E00BA8D9E for ; Mon, 17 Aug 2015 18:35:10 +0200 (CEST) Received: from pps.filterd (m0002317.ppops.net [127.0.0.1]) by mx0b-00103a01.pphosted.com (8.14.5/8.14.5) with SMTP id t7HGYsm2027291; Mon, 17 Aug 2015 12:35:10 -0400 Received: from vawvcgsie2k1301.ciena.com (LIN1-118-36-35.ciena.com [63.118.36.35]) by mx0b-00103a01.pphosted.com with ESMTP id 1w92uhsd5n-1 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 17 Aug 2015 12:35:09 -0400 Received: from ONWVEXCHHT01.ciena.com (10.128.6.16) by VAWVCGSIE2K1301.ciena.com (10.4.62.15) with Microsoft SMTP Server (TLS) id 15.0.847.32; Mon, 17 Aug 2015 12:35:08 -0400 Received: from ONWVEXCHMB01.ciena.com ([10.128.6.18]) by ONWVEXCHHT01.ciena.com ([::1]) with mapi; Mon, 17 Aug 2015 12:35:08 -0400 From: "Yeddula, Avinash" To: "Singh, Jasvinder" , "Richardson, Bruce" Date: Mon, 17 Aug 2015 12:35:06 -0400 Thread-Topic: [dpdk-dev] [ 2nd try ] Lookup mechanim in DPDK HASH table. Thread-Index: AdDWEC6OvyssoEwzRkW/rjWnlKZeIQAWoiAAAKCu8WAABs0O8A== Message-ID: References: <20150814092502.GA8916@bricha3-MOBL3> <54CBAA185211B4429112C315DA58FF6DD265C4@IRSMSX103.ger.corp.intel.com> In-Reply-To: <54CBAA185211B4429112C315DA58FF6DD265C4@IRSMSX103.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US x-tm-as-product-ver: SMEX-10.0.0.1412-7.000.1014-21752.001 x-tm-as-result: No--49.525000-8.000000-31 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.14.151, 1.0.33, 0.0.0000 definitions=2015-08-17_03:2015-08-17,2015-08-17,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1508030000 definitions=main-1508170266 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 16:35:11 -0000 + Mike ( My team mate) Hi Jasvinder, It's not a bidirectional packet flow. The pipeline looks some= thing like this. Ingress port-----Table 1 ----Table-2 ----- Mac_Table ----- Table4 ---- Egre= ss 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 d= st lookup success). Here are the keys we are using. Src lookup key - Src MAC (src MAC in the frame) + Bridge ID ( Bridge on w= hich it arrived). Dst lookup key - Dst MAC (dst MAC in the frame) + Bridge ID ( Bridge on wh= ich it arrived) Thanks -Avinash -----Original Message----- From: Singh, Jasvinder [mailto:jasvinder.singh@intel.com]=20 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. >=20 > 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,=20 > > 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=20 > > to the > lookup aspect of the hash table. > > I see that there is just one "t->key_offset" that is pre-defined for=20 > > the hash > table. I also understand that the frame needs to carry the "lookup_key=20 > / keys" in the meta data. > > > > Here is my question: How to support more than one lookup with=20 > > 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 >=20 > Just to confirm: this is using the extensible bucket hash in the=20 > rte_table library of packet framework, rather than the standalone=20 > rte_hash library, right? >=20 > /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 des= tination, symmetric hash can be used- http://www.ndsl.kaist.edu/~kyoungsoo= /papers/TR-symRSS.pdf=20 Jasvinder