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 BFDDA8D8B for ; Sat, 26 Sep 2015 00:26:44 +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 t8PMOotm015242 for ; Fri, 25 Sep 2015 18:26:43 -0400 Received: from vawvcgsie2k1301.ciena.com (LIN1-118-36-35.ciena.com [63.118.36.35]) by mx0b-00103a01.pphosted.com with ESMTP id 1x59w4h19q-1 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for ; Fri, 25 Sep 2015 18:26:43 -0400 Received: from VAWVE2K13MBX01.ciena.com (10.4.156.87) by VAWVCGSIE2K1301.ciena.com (10.4.62.15) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 25 Sep 2015 18:26:42 -0400 Received: from ONWVEXCHHT03.ciena.com (10.128.6.43) by VAWVE2K13MBX01.ciena.com (10.4.156.87) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 25 Sep 2015 18:26:42 -0400 Received: from ONWVEXCHMB01.ciena.com ([10.128.6.18]) by ONWVEXCHHT03.ciena.com ([::1]) with mapi; Fri, 25 Sep 2015 18:26:41 -0400 From: "Yeddula, Avinash" To: "dev@dpdk.org" Date: Fri, 25 Sep 2015 18:26:40 -0400 Thread-Topic: Need your thoughts on DPDK hash table / DPDK lookup/insert API's Thread-Index: AdD34TS+v3QRYXIySDinG5KvTy34Ww== Message-ID: Accept-Language: en-US, en-CA Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-CA x-tm-as-product-ver: SMEX-10.0.0.1412-7.000.1014-21838.003 x-tm-as-result: No--41.809600-8.000000-31 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No 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-09-25_12:2015-09-25,2015-09-25,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-1509250329 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Need your thoughts on DPDK hash table / DPDK lookup/insert API's 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: Fri, 25 Sep 2015 22:26:45 -0000 Hello All, 1. I've a scenario where I need to walk the entire Hash table to retri= eve the data. I'm currently using DPDK extensible bucket hash in the rte_t= able library of packet framework. Since I'll not be storing the keys anywhere else, I don't have a way to wal= k 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 pi= peline 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 ev= erything 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 lo= okup API to act " static int rte_table_array_single_pkt_lookup( void *table, void *key, v= oid *entry) Any thoughts on adding these 2 items officially to dpdk library. Thanks -Avinash