From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 478B3A054F; Wed, 10 Feb 2021 15:26:44 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 027B640693; Wed, 10 Feb 2021 15:26:44 +0100 (CET) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by mails.dpdk.org (Postfix) with ESMTP id 09CBF40142 for ; Wed, 10 Feb 2021 15:26:42 +0100 (CET) IronPort-SDR: ZJkKsG0dBtgh6K52j9I35fi1IzgXRZiM/qj9BfnbIDVaxV0cTwPXZ6mrHwgBZbcvEPxUVuPeyz mzCvUUr16J8w== X-IronPort-AV: E=McAfee;i="6000,8403,9890"; a="169754716" X-IronPort-AV: E=Sophos;i="5.81,168,1610438400"; d="scan'208";a="169754716" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Feb 2021 06:26:41 -0800 IronPort-SDR: NqSVYRMkZ5EUVa7qMOgMc+PwZ1bQCJoyw49uoHZWrHMuWi5Ne54xjdbV0zgHf+7iZaMQCYmSCE SMFKqV4NbiMg== X-IronPort-AV: E=Sophos;i="5.81,168,1610438400"; d="scan'208";a="396722053" Received: from vmedvedk-mobl.ger.corp.intel.com (HELO [10.213.202.132]) ([10.213.202.132]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Feb 2021 06:26:35 -0800 To: "Burakov, Anatoly" , Tal Shnaiderman , dev@dpdk.org Cc: thomas@monjalon.net, pallavi.kadam@intel.com, dmitry.kozliuk@gmail.com, navasile@linux.microsoft.com, dmitrym@microsoft.com, david.marchand@redhat.com References: <20210106194543.14024-1-talshn@nvidia.com> <20210106203553.9876-1-talshn@nvidia.com> <20210106203553.9876-3-talshn@nvidia.com> From: "Medvedkin, Vladimir" Message-ID: Date: Wed, 10 Feb 2021 14:26:33 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v9 2/2] eal: add generic thread-local-storage functions X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Tal, On 10/02/2021 13:33, Burakov, Anatoly wrote: > On 06-Jan-21 8:35 PM, Tal Shnaiderman wrote: >> Add support for TLS functionality in EAL. >> >> The following functions are added: >> rte_thread_tls_key_create - create a TLS data key. >> rte_thread_tls_key_delete - delete a TLS data key. >> rte_thread_tls_value_set - set value bound to the TLS key >> rte_thread_tls_value_get - get value bound to the TLS key >> >> TLS key is defined by the new type rte_tls_key. I would suggest changing rte_tls_key to rte_thread_tls_key so that it is consistent with the API and not confused with transport layer security. >> >> The API allocates the thread local storage (TLS) key. >> Any thread of the process can subsequently use this key >> to store and retrieve values that are local to the thread. >> >> Those functions are added in addition to TLS capability >> in rte_per_lcore.h to allow abstraction of the pthread >> layer for all operating systems. >> >> Windows implementation is under librte_eal/windows and >> implemented using WIN32 API for Windows only. >> >> Unix implementation is under librte_eal/unix and >> implemented using pthread for UNIX compilation. >> >> Signed-off-by: Tal Shnaiderman >> --- > -- Regards, Vladimir