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 19E4341BBD; Fri, 3 Feb 2023 15:55:57 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A42B74067B; Fri, 3 Feb 2023 15:55:56 +0100 (CET) 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 EA9754021E for ; Fri, 3 Feb 2023 15:55:54 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1675436154; 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=fUXxAzoFrkMdAL5zaDqDh1V4JxSf9EbMEMVkU4uhoM4=; b=WYRdnflVDYJTjGGFfLgZKeGbFrcO41vPziBBorZjOPf9FuDq9Rhh9tKF76a/zHGzRfb80U ob/bufSwOAt827boZK7KlBm0REL+G6WZIWqE+H8XMzzS9qfeq2PGfN5egojYw9Cz4/SULN G6I7Z/RxvzCQHXHfvzSKoL7sneUOnSw= 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-384-aC9PQrdyNO2p0B_tgDez5Q-1; Fri, 03 Feb 2023 09:55:51 -0500 X-MC-Unique: aC9PQrdyNO2p0B_tgDez5Q-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 00356811E6E; Fri, 3 Feb 2023 14:55:51 +0000 (UTC) Received: from [10.39.208.28] (unknown [10.39.208.28]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 4643D7AD4; Fri, 3 Feb 2023 14:55:50 +0000 (UTC) Message-ID: <3f9e59c7-0f13-c45a-7f10-593c90deaf81@redhat.com> Date: Fri, 3 Feb 2023 15:55:48 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Subject: Re: [PATCH] vdpa/ifc: improve device stop logic for block device To: Andy Pei , dev@dpdk.org Cc: chenbo.xia@intel.com References: <1670917055-229334-1-git-send-email-andy.pei@intel.com> From: Maxime Coquelin In-Reply-To: <1670917055-229334-1-git-send-email-andy.pei@intel.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 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 12/13/22 08:37, Andy Pei wrote: > For block device, we make sure no IO is inflight before we > stop device. We terminate the notify relay process and wait > for all inflight IOs to be completed. So in this period, we > wait for hardware to update used index, there is no need to > relay new kick. > > Signed-off-by: Andy Pei > --- > drivers/vdpa/ifc/ifcvf_vdpa.c | 6 +----- > 1 file changed, 1 insertion(+), 5 deletions(-) > Applied to dpdk-next-virtio/main. Thanks, Maxime