From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 1CCF1378E for ; Sun, 18 Sep 2016 10:16:15 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga104.jf.intel.com with ESMTP; 18 Sep 2016 01:16:14 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,355,1470726000"; d="scan'208";a="1058381981" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by fmsmga002.fm.intel.com with ESMTP; 18 Sep 2016 01:16:13 -0700 Date: Sun, 18 Sep 2016 16:16:43 +0800 From: Yuanhan Liu To: John Griffin Cc: dev@dpdk.org, eoin.breen@intel.com, pablo.de.lara.guarch@intel.com Message-ID: <20160918081643.GE23158@yliu-dev.sh.intel.com> References: <1472725298-8455-1-git-send-email-john.griffin@intel.com> <20160905032356.GH30752@yliu-dev.sh.intel.com> <57D96D9E.8040301@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57D96D9E.8040301@intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) 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: Sun, 18 Sep 2016 08:16:16 -0000 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