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 83252A0C4B for ; Thu, 21 Oct 2021 14:27:36 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 79F0F4118E; Thu, 21 Oct 2021 14:27:36 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id 21F014118E for ; Thu, 21 Oct 2021 14:27:35 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1634819254; 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=mMKmNRG00d4TRpFzNdwOfRb8EhpAcS97NRFEYPnPkBs=; b=PHphMVaoHVZ+O0DWzb9q7MkV5Nd5kuIOd64JZzhvtQiQzvruDmMfCjVz/BOUovkcu/18iX hp/hQuk9pjUPKJ/LSbFNxr4WqbF8ocg2okI66cLAwQDkXxvEmakxjx7bIzJiL0iJ8yuZ49 XePiSdSKIyTqVIHEKQcoh408Gi8A2dg= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-595-kvJuFznRPzynX4mpA5s5-A-1; Thu, 21 Oct 2021 08:27:31 -0400 X-MC-Unique: kvJuFznRPzynX4mpA5s5-A-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 40339101B4A0; Thu, 21 Oct 2021 12:27:30 +0000 (UTC) Received: from [10.39.208.27] (unknown [10.39.208.27]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 931A46A75A; Thu, 21 Oct 2021 12:27:28 +0000 (UTC) Message-ID: <5cf3ad7d-0210-1fe9-b852-4cc81aedc772@redhat.com> Date: Thu, 21 Oct 2021 14:27:26 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.1.0 To: Xueming Li , dev@dpdk.org Cc: stable@dpdk.org, Matan Azrad , Viacheslav Ovsiienko References: <20210923081758.178745-1-xuemingl@nvidia.com> <20211015150545.1673312-1-xuemingl@nvidia.com> <20211015150545.1673312-2-xuemingl@nvidia.com> From: Maxime Coquelin In-Reply-To: <20211015150545.1673312-2-xuemingl@nvidia.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 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 Subject: Re: [dpdk-stable] [PATCH v2 2/2] vdpa/mlx5: retry VAR allocation during vDPA restart X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" On 10/15/21 17:05, Xueming Li wrote: > VAR is the device memory space for the virtio queues doorbells, qemu > could mmap it to directly to speed up doorbell push. > > On a busy system, Qemu takes time to release VAR resources during driver > shutdown. If vdpa restarted quickly, the VAR allocation failed with > error 28 since the VAR is singleton resource per device. > > This patch adds retry mechanism for VAR allocation. > > Fixes: 4cae722c1b06 ("vdpa/mlx5: move virtual doorbell alloc to probe") > Cc: stable@dpdk.org > > Signed-off-by: Xueming Li > Reviewed-by: Matan Azrad > --- > drivers/vdpa/mlx5/mlx5_vdpa.c | 9 ++++++++- > 1 file changed, 8 insertions(+), 1 deletion(-) Applied to dpdk-next-virtio/main. Thanks, Maxime