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 DE3D2A00C3; Fri, 17 Jun 2022 16:27:42 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B663242B70; Fri, 17 Jun 2022 16:27:42 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id DA51240F19 for ; Fri, 17 Jun 2022 16:27:40 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1655476060; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rIuGbahuyNeJdOQ8QfVX9KUs0ZRzpS+lOZRrfv+XAv4=; b=IxRLqdoPr40S6g31fvyOsSsTz53tRaRrok3G7+xmuJV1C6e1bcfEbZxqvaQ6eS7mSZocSn PXOmW/fmWWTEAPvtOh0ew7sXsQjxjzvQnqwuD68SHeyNmEy0rf822L9CadH/FkHnfuKpB3 +sbNXxQtaRKc17OsyOHn8DelnDz5bWA= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-636-g2EPACdFPSCL8DuAPh6qqQ-1; Fri, 17 Jun 2022 10:27:23 -0400 X-MC-Unique: g2EPACdFPSCL8DuAPh6qqQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 25EFD81F30D; Fri, 17 Jun 2022 14:27:23 +0000 (UTC) Received: from [10.39.208.34] (unknown [10.39.208.34]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 48B8BC44CC3; Fri, 17 Jun 2022 14:27:21 +0000 (UTC) Message-ID: <0980f8a5-86c5-4ebd-d9d7-8f9e43c6e9b5@redhat.com> Date: Fri, 17 Jun 2022 16:27:19 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [PATCH v2 01/15] vdpa/mlx5: fix usage of capability for max number of virtqs To: Li Zhang , orika@nvidia.com, viacheslavo@nvidia.com, matan@nvidia.com, shahafs@nvidia.com Cc: dev@dpdk.org, thomas@monjalon.net, rasland@nvidia.com, roniba@nvidia.com, stable@dpdk.org References: <20220408075606.33056-1-lizh@nvidia.com> <20220616023012.16013-1-lizh@nvidia.com> <20220616023012.16013-2-lizh@nvidia.com> From: Maxime Coquelin In-Reply-To: <20220616023012.16013-2-lizh@nvidia.com> X-Scanned-By: MIMEDefang 2.85 on 10.11.54.8 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=maxime.coquelin@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 On 6/16/22 04:29, Li Zhang wrote: > The driver wrongly takes the capability value for > the number of virtq pairs instead of just the number of virtqs. > > Adjust all the usages of it to be the number of virtqs. > > Fixes: c2eb33a ("vdpa/mlx5: manage virtqs by array") > Cc: stable@dpdk.org > > Signed-off-by: Li Zhang > Acked-by: Matan Azrad > --- > drivers/vdpa/mlx5/mlx5_vdpa.c | 12 ++++++------ > drivers/vdpa/mlx5/mlx5_vdpa_virtq.c | 6 +++--- > 2 files changed, 9 insertions(+), 9 deletions(-) > Reviewed-by: Maxime Coquelin Thanks, Maxime