From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 5BA65A0C43;
	Fri, 26 Nov 2021 13:28:57 +0100 (CET)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 458E04272D;
	Fri, 26 Nov 2021 13:28:57 +0100 (CET)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com
 [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id 28EF040C35
 for <dev@dpdk.org>; Fri, 26 Nov 2021 13:28:56 +0100 (CET)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46])
 by mailout.nyi.internal (Postfix) with ESMTP id CEE795C00D4;
 Fri, 26 Nov 2021 07:28:54 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162])
 by compute6.internal (MEProxy); Fri, 26 Nov 2021 07:28:54 -0500
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=fm2; bh=
 EGWzMcWXxEmfGp4lcJR+o0yX+xD0OyvAwp8IhBfLpZs=; b=GjnXK41D7tH9bvr6
 6NyubHFK0aq+2Qzomytu6B753S0PU9Pr9Vm+5ywcCj46vm7rn6Sn8jN1wR28spnC
 IVDJcphBPsjYgpcO7EsyPSTgX69TopuIgHi+GzAC7IY0iKyvFGP3aQ34KnCTCu1f
 hNBXP2BKvCZuBmHmC3AaYVGgRv6/U8muemnHCAbyqo02Z4C7t3aNeq4r96pjTDcn
 oAcaDKGfMYbx+5VxjhJbJtDbAMRlxj9BrqFLFA3eAhMAD+5kXDWGnbT8vdG65/9B
 n5teS3cs4Mi2cfm4KsJ1QS7xFPBqX1c1FeJDyI7FTkbZyomIvFGZ5EZelZmD+Qdk
 5sSeHw==
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=fm1; bh=EGWzMcWXxEmfGp4lcJR+o0yX+xD0OyvAwp8IhBfLp
 Zs=; b=nrIgXmfJ0Nj9Nwk2ba4IYmXp5GZ7AwwjSaZdSHeyY++ZFelSZWaaPlEB0
 811Ij4ECZV9P9OQuQp4v/TlETrKd/ZL9zualp5DGOdNKYGe7ySs+8W6nowFlDcmi
 gMVWzEhcX8qd9NRxM8Er21iVsLd/t4mrSysspMKNQhWUNwZy2kb5KN919NJbGVjD
 AtqxywxsHo/v2QfJUcPcKPQpOZOMJwpJP8dO1EbFrRuV1fxNh9e8bJ+y37uRG2bn
 lrM8LOkrCI0994wZw258YfQFd9QcwUUUut54JQ1dVUEBwLXO6RprBYSmIJVXhVdM
 RvDOKtjZ92tRyOT5iBq+v0fJhR0vA==
X-ME-Sender: <xms:BtOgYaUw9PV3WtC83_hqq0bbO6U5Mtl12TN9UxCPC8qQI4N1V_F0DQ>
 <xme:BtOgYWkQv1LCxbFJY7qoZohoqK5PFWoUITSyElBLSyt-gr5wRmsbojdUIwVgEVu65
 TkUOSRYh5gjeMWnDA>
X-ME-Received: <xmr:BtOgYeaqRAoWYCQrFrmOKz5epaWA6qVWVQik10GOQC21nHyqL5VTg6LEP4F4xYS9OYOEt9CwmMEYASDLI-SkqjzAcA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrhedvgdeflecutefuodetggdotefrodftvf
 curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu
 uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc
 fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs
 ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf
 frrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdejueei
 iedvffegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh
 hmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght
X-ME-Proxy: <xmx:BtOgYRXUslUT_Atf_QleXMepUZ8hnx5RM9aHgnuZyMlAF8mpa2YjaA>
 <xmx:BtOgYUnvTh3df1jI3y_jb-RYEnuqmJWLJRBpQwu_SxufdRQJgb6D2g>
 <xmx:BtOgYWcUysv2XN7SngvdAavJcG0K8HXFPbwlbfb7622CpZe3S3ywXg>
 <xmx:BtOgYej_Q5nqF9uj0jPyQ8zqeVK045qXB9335zic3YnsLssgHL3CBw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri,
 26 Nov 2021 07:28:53 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Raslan Darawsheh <rasland@nvidia.com>,
 Matan Azrad <matan@nvidia.com>, Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [PATCH] common/mlx5: fix MR lookup on slow path
Date: Fri, 26 Nov 2021 13:28:48 +0100
Message-ID: <6913098.DbvkNnyOu5@thomas>
In-Reply-To: <DM6PR12MB37530FB8BBA011D21F005825DF639@DM6PR12MB3753.namprd12.prod.outlook.com>
References: <20211125202044.3483813-1-dkozlyuk@nvidia.com>
 <DM6PR12MB37530FB8BBA011D21F005825DF639@DM6PR12MB3753.namprd12.prod.outlook.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

> > Memory region (MR) was being looked up incorrectly for the data address of
> > an externally-attached mbuf.
> > A search was attempted for the mempool of the mbuf, while mbuf data
> > address does not belong to this mempool in case of externally-attached mbuf.
> > Only attempt the search:
> > 1) for not externally-attached mbufs;
> > 2) for mbufs coming from MPRQ mempool;
> > 3) for externally-attached mbufs from mempools
> >    with pinned external buffers.
> > 
> > Fixes: 08ac03580ef2 ("common/mlx5: fix mempool registration")
> > 
> > Signed-off-by: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
> > Reviewed-by: Matan Azrad <matan@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

Applied as last-minute critical fix.