From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id C79B3A034F; Wed, 6 May 2020 12:14:38 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id ACEF61D8E4; Wed, 6 May 2020 12:14:38 +0200 (CEST) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id 67E331D8E0 for ; Wed, 6 May 2020 12:14:37 +0200 (CEST) IronPort-SDR: CDynfPhtkFbFgCNHDN1KRIkedIdOHCkFQXUq2gScbiK2Ef+IEnAZaVRL9pwHvzgW4o7Jl+mVUT TU2h3i9UKstw== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 May 2020 03:14:33 -0700 IronPort-SDR: wkbBLxjdJhNcdy1JAbPuhwEuvE1ZD3c8CwqgllAjv4o3SHIu53lmDijfCujpmlz2Tt7ICV6/il uv32fZRH4FIQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.73,358,1583222400"; d="scan'208";a="338959698" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.209.121.37]) ([10.209.121.37]) by orsmga001.jf.intel.com with ESMTP; 06 May 2020 03:14:32 -0700 To: Renata Saiakhova , Lukasz Wojciechowski , "dev@dpdk.org" References: <20200503162636.5233-1-Renata.Saiakhova@ekinops.com> <20200503162636.5233-2-Renata.Saiakhova@ekinops.com> From: "Burakov, Anatoly" Message-ID: Date: Wed, 6 May 2020 11:14:31 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH 1/2] librte_ethdev: Introduce a function to release HW rings X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 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" On 05-May-20 6:25 PM, Renata Saiakhova wrote: > Hi Lukasz, > > thanks for your comments! I understand Anatoly is going to to make a fix > rather in memzone API level, to introduce atomic "find and allocate" and > "find and free" operations, so this patch code won't stay long and in > this case maybe better not to disturb the original code of > rte_eth_dma_zone_reserve() ? Just a question. > I wouldn't really count on that API appearing in stable any time soon, so i suggest proceeding with your approach. -- Thanks, Anatoly