From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id F11AF292D for ; Mon, 19 Sep 2016 12:12:40 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga102.jf.intel.com with ESMTP; 19 Sep 2016 03:12:17 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,361,1470726000"; d="scan'208";a="763204203" Received: from sie-lab-212-151.ir.intel.com (HELO [10.237.212.151]) ([10.237.212.151]) by FMSMGA003.fm.intel.com with ESMTP; 19 Sep 2016 03:12:16 -0700 To: Yuanhan Liu References: <1472725298-8455-1-git-send-email-john.griffin@intel.com> <20160905032356.GH30752@yliu-dev.sh.intel.com> <57D96D9E.8040301@intel.com> <20160918081643.GE23158@yliu-dev.sh.intel.com> Cc: dev@dpdk.org, eoin.breen@intel.com, pablo.de.lara.guarch@intel.com From: John Griffin Message-ID: <57DFB9FF.5090907@intel.com> Date: Mon, 19 Sep 2016 11:12:15 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <20160918081643.GE23158@yliu-dev.sh.intel.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] crypto/qat: fix memzone creation to use a fixed size string 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, 19 Sep 2016 10:12:41 -0000 On 18/09/16 09:16, Yuanhan Liu wrote: > On Wed, Sep 14, 2016 at 04:32:46PM +0100, John Griffin wrote: >> Hi Liu, >> Comments embedded. >> >> Rgds, >> John. >> >> On 05/09/16 04:23, Yuanhan Liu wrote: >>> On Thu, Sep 01, 2016 at 11:21:38AM +0100, John Griffin wrote: >>>> Remove the dependency on dev->driver->pci_drv.name when >>>> creating the memzone for the qat hardware queues. >>>> The pci_drv.name may grow too large for RTE_MEMZONE_NAMESIZE. >>> >>> Will the "may grow too large" cause any issues? If so, state it here. If >>> not, marking this patch as a "fix" patch doesn't make sense to me then. >> We discovered this when applying a future patch (2141c21966) and it exposed >> this issue. >> Problem is we create a memzone per hardware queue pair and if the memzone >> name is too large, then this code will not produce a unique >> name and two qps will end using the same memzone. > > Thanks for the info, and I think you should put it in the commit log: it > helps people to really know what might go wrong without this fix. > > --yliu > No problem. Yes will add to the v2. Rgds, John.