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 103AFA00E6 for ; Sun, 7 Jul 2019 19:24:37 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id DE246324D; Sun, 7 Jul 2019 19:24:35 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 2DFD13237 for ; Sun, 7 Jul 2019 19:24:34 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 5AD3121C24; Sun, 7 Jul 2019 13:24:33 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 07 Jul 2019 13:24:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=pph1gKjx4paWgAp9sKv4oOH2BdXFV9nD70Y43BIIiL0=; b=KcbgDNrQGdSM D5HrdV3j+8AHrsZ9+iWVv0b2Zga0rXlbgykVwblBynJ+lHf6WQZYEHJaoLHb6RR5 HK3+oJfsONmAIRuFJ5oVbutly0Z+SrB0qEXGNxZ8vDoA7aAwLlWETR51mf4Hw3fQ qybLMhqF40fjv918B23Qftw7jC4FnmY= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=pph1gKjx4paWgAp9sKv4oOH2BdXFV9nD70Y43BIIi L0=; b=bOXMLiLA3gq1NYVbvfPp3OyhEnwc0ge1wv9iX0JN4GxUC6Jzx5qMYBg1c iQAZtnU3XlqnUsWB/69qIOCmCuY6kukcN+56a2K1kngIPpcFIJRQODq1KF1Cmn0C sgIY1alrWyqEDFVj48xOboYUOfoBfN54T7LPEXHFuBfYuT2+cvscnFm1YUT5+Y01 B8x7XoQQEEjjgU1xatiuTz2Ut7H49Atjtth206rEj3BO82YOU8KvzQVzTD08QiFs 4Luw2tZR2GD8iN/p4tWGdj6BVkHwUX4B3n2L0cXwqzeEFj1sbZvxkq8+7YUtnvfI sWqrjn8hanMI1GNvjw/SKy02bpA8Q== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrfeekgdduudeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 59E01380075; Sun, 7 Jul 2019 13:24:32 -0400 (EDT) From: Thomas Monjalon To: Vamsi Krishna Attunuru Cc: Jerin Jacob Kollanukkaran , "dev@dpdk.org" Date: Sun, 07 Jul 2019 19:24:26 +0200 Message-ID: <2282525.4GGbi3Xbp4@xps> In-Reply-To: References: <20190705103341.30219-1-vattunuru@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v1 1/1] mempool/octeontx2: fix npa pool range errors 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" 07/07/2019 16:21, Jerin Jacob Kollanukkaran: > > > -----Original Message----- > > From: vattunuru@marvell.com > > Sent: Friday, July 5, 2019 4:04 PM > > To: dev@dpdk.org > > Cc: thomas@monjalon.net; Jerin Jacob Kollanukkaran ; > > Vamsi Krishna Attunuru > > Subject: [PATCH v1 1/1] mempool/octeontx2: fix npa pool range errors > > > > From: Vamsi Attunuru > > > > Patch fixes npa pool range errors observed while creating mempool. > > During mempool creation, octeontx2 mempool driver populates pool range > > fields before enqueueing the buffers. If any enqueue or dequeue operation > > reaches npa hardware prior to the range field's HW context update, those ops > > result in npa range errors. Patch adds a routine to read back HW context and > > verify if range fields are updated or not. > > > > Signed-off-by: Vamsi Attunuru > > > 1) Please fix chek-git-log.sh > > $ ./devtools/check-git-log.sh > Missing 'Fixes' tag: > mempool/octeontx2: fix npa pool range errors > > 2) Please mention this issue happens when mempool objects are > from different mempool in git commit log One more comment, the title is supposed to say which behaviour it is fixing, not the root cause.