From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 19E5AA0A02; Tue, 18 May 2021 10:32:50 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 877004068E; Tue, 18 May 2021 10:32:49 +0200 (CEST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id 68DBE40041; Tue, 18 May 2021 10:32:48 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id E7D975C00D9; Tue, 18 May 2021 04:32:47 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 18 May 2021 04:32:47 -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=fm1; bh= WNAfzfBNjOyy5izaToe1OFfqqPNiOFns0OwW7V3QqRg=; b=JJZLKNLcjG4BysSP pIAqlQqM2im1tR4hnk/DAL9N/B9NTNwC2kPEUEF4Ym0Au9YmxtzLIrgxrx+DI6C4 +OmsBqf4Ggp/3RJ5/2Qv/n6wPFfE/r4UGsXYXbuvzQKzzzA02V4bjTVUp6465Xcj nwkVusD+ueYqJvaPmlTM6Zy3N4HD2BId+X9MBe/wwWF7ghtCJKesDaKUYfnxK2UJ gJeOEhqJVidXZ599yY9NKC9Rbx+OAExMfdbO6QMYJ1nGOp06t1s4glavrUwp+nJ5 7M1h7ZSsVoRLwfHd47r5hr3XOBBIsNNYtiow58KK/5O7h6b7VSZxfqk21uG02XUb z0CuQw== 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=fm2; bh=WNAfzfBNjOyy5izaToe1OFfqqPNiOFns0OwW7V3Qq Rg=; b=k7F08jUDdyRu+e6TETvUKlrksGPDndoPWz9nEtiZsY8WyrKngagmS1jHR nGCcPvVQTDAdsBXxdICSjfXTajMrL2zJpfaLKZEpY5uBPgq/+7/UY7bHK3w1735b lCdLbLupHOj7wKZ/sUbXNX+ViIhG0ke9FJYMU7JJ9vbMQyiI6OyujtvQoOhgxNt3 Lq8CgbKpeOQGZB63PCKuWsWTI19ElD6Nd8cbSSiR8QtxBI3SAFWCo4e+MQbnwjrQ Uc6lS8Jd+wSzn5i+SQNVVVZzZHOelTX80g2RGyvWSYhYT8VNdUgrzghAMcW6OLlg zOqmb4VUDS7rW1Qv0VwQdyS6M14hw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdeijedgtdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvght 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; Tue, 18 May 2021 04:32:46 -0400 (EDT) From: Thomas Monjalon To: Bing Zhao Cc: viacheslavo@nvidia.com, matan@nvidia.com, dev@dpdk.org, orika@nvidia.com, rasland@nvidia.com, stable@dpdk.org, talshn@nvidia.com Date: Tue, 18 May 2021 10:32:45 +0200 Message-ID: <3881058.ArAt7a84xB@thomas> In-Reply-To: <20210517151841.57847-1-bingz@nvidia.com> References: <20210512143607.3982046-1-bingz@nvidia.com> <20210517151841.57847-1-bingz@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3] net/mlx5: fix loopback for DV queue X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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" 17/05/2021 17:18, Bing Zhao: > In the past, all the queues and other hardware objects were created > through Verbs interface. Currently, most of the objects creation are > migrated to Devx interface by default, including queues. Only when > the DV is disabled by device arg or eswitch is enabled, all or some > of the objects are created through Verbs interface. > > When using Devx interface to create queues, the kernel driver > behavior is different from the case using Verbs. The Tx loopback > cannot work properly even if the Tx and Rx queues are configured > with loopback attribute. To fix the support self loopback for Tx, a > Verbs dummy queue pair needs to be created to trigger the kernel to > enable the global loopback capability. > > This is only required when TIR is created for Rx and loopback is > needed. Only CQ and QP are needed for this case, no WQ(RQ) needs to > be created. > > This requirement comes from bugzilla 645, more details can be found > in the bugzilla link. > > Bugzilla ID: 645 > > Fixes: 6deb19e1b2d2 ("net/mlx5: separate Rx queue object creations") > Cc: stable@dpdk.org > > Signed-off-by: Bing Zhao > Acked-by: Viacheslav Ovsiienko Applied to next-net-mlx, thanks.