From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f97.google.com (mail-lf0-f97.google.com [209.85.215.97]) by dpdk.org (Postfix) with ESMTP id 69CF4952 for ; Wed, 8 Feb 2017 11:55:30 +0100 (CET) Received: by mail-lf0-f97.google.com with SMTP id x1so10727141lff.0 for ; Wed, 08 Feb 2017 02:55:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verint-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:thread-topic:thread-index:date:message-id :accept-language:mime-version:content-language; bh=0XQ38fZHmZOR8sTi4l0e4MC9ebG3QzSCXJptRtkLFVs=; b=QuLZ1O2K8A9HDYbMuvGB9JK2WMujULfWG+cz3jJ6ABV50oIt0dRcyHi46KMD0/simO XbJIZhvzWZsazFnQ7dyq4lBY+AUYfPykr9R0wyJzgGLYjyMCDZ3KLuGyjmDvh8xgUWU9 E8hWGMJwkyH7DA40OAb+BBJO6jU2mau9HlmhpEt8IkxC3LaSl8Of7dxxRNuBRu8W2eyd t0gAbg+tKxLHknDkyVTr5kZmq72fWAWwyWtaNThLLfj1WP5Y0W9BPn8mT+Rm77NgFEB9 7mZ64szSkg8GUnA3d9UDerBel6o8JeL00yRGCteuzoju3oGjYoCxAR3Cu5C2sARFpTPF yrfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:accept-language:mime-version:content-language; bh=0XQ38fZHmZOR8sTi4l0e4MC9ebG3QzSCXJptRtkLFVs=; b=Ew0t2HEgI/WsmAHKIufCKFsGE4Sg0dMCcdCLetQVRLjs5Co3FrcbfA2MJAcnCdo8Ve +sjUwJSqF+OvSa2x0dqWrYoxCyaqXwfe3crwtvUL6wyx4ilBWWm+ai/szPjQlBZSpR14 uerGsxDVsp4bCuv47xs8RaLDtKdI254ij7imtNeiovxWjYtHpm7ePzoSZ7mTKoUAXhA3 T0ZeLkK95ELxpUinXEeOTIicJlxjUEDfkr9oppI0T9lt3EPMvR472JP37lZCAHx2yYml UwFEIVbaVgkrlJwva4vcdcs4RsG0G2d/aM15tmxHBl/yw8XR2u9d7jUAIiHsTsRqhrHT KPZQ== X-Gm-Message-State: AIkVDXLS7MgpiFMAQbH0Soo8Q1s3dVil+a4ngEietMSJ1Pj56iVX0r1wWjXUrWGwKtG0jQO209VvsBH8/cZvo7gReGwAi765jGPFVK4SL6aLmSmdrkL+sT2Rq9q3XfcXVJqEWRli/hdMo9j1nJw2MAmja95X9uK1RwBwkmY3zt+pXZXGOhh6SmaG1BzCvFsjV8jD X-Received: by 10.223.147.100 with SMTP id 91mr17953543wro.5.1486551329911; Wed, 08 Feb 2017 02:55:29 -0800 (PST) Received: from mail.verint.com ([193.27.93.18]) by smtp-relay.gmail.com with ESMTPS id h73sm180895wme.3.2017.02.08.02.55.29 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 08 Feb 2017 02:55:29 -0800 (PST) X-Relaying-Domain: verint.com Received: from TLVCAS3.Verint.Corp.Verintsystems.com (10.61.241.147) by TLVCAS2.verint.corp.verintsystems.com (10.61.241.145) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 8 Feb 2017 12:55:10 +0200 Received: from TLVMBX2.Verint.Corp.Verintsystems.com ([169.254.3.12]) by TLVCAS3.verint.corp.verintsystems.com ([::1]) with mapi id 14.03.0319.002; Wed, 8 Feb 2017 12:55:10 +0200 From: "Bar, Nir" To: "users@dpdk.org" Thread-Topic: rte_hash_hash in DPDK2.0 Thread-Index: AdKB+dDXSp7f0BFKTEOjeZIAbwcSBw== Date: Wed, 8 Feb 2017 10:55:10 +0000 Message-ID: <33C55E1E4B8F6F44A79984DB4C8FD76DF35E5A54@TLVMBX2.verint.corp.verintsystems.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.61.241.157] MIME-Version: 1.0 Content-Language: en-US Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] rte_hash_hash in DPDK2.0 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 10:55:30 -0000 Hi, Why rte_has_hash() in DPDK-2.0 isn't multi thread safe? It only calculates hash. Thanks, Nir ** * Calc a hash value by key. This operation is not multi-process safe. * * @param h * Hash table to look in. * @param key * Key to find. * @return * - hash value */ static inline hash_sig_t rte_hash_hash(const struct rte_hash *h, const void *key) { /* calc hash result by key */ return h->hash_func(key, h->key_len, h->hash_func_init_val); } -- This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries. The information is intended to be for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message. If you have received this electronic message in error, please notify us by replying to this e-mail.