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 CF894A0093; Tue, 14 Jun 2022 15:23:42 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 75F8440DDD; Tue, 14 Jun 2022 15:23:42 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id C318D40A81 for ; Tue, 14 Jun 2022 15:23:40 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1655213020; 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=qtzFs//JUmTpXgsdCMwTZIFVvUy7ZHbocZM78LNu2HI=; b=gy5ivHmk4AtNRUmcysO0HA9+Y2y/kdTjEESZOIRj6IxWHshWbmg8obcK/FS2CBhcSG9LxF sikw7BIwLdYs+DeV78biAytVJDdVFGctJznssGJGVy5DbPxhAlbTsVq7iPEQ+tqDwWUFSi AmjtNyY9jy1NK2kGRhEJRr32rI4H8RM= 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-655-cNJ9xJ4nMleKRuB2aLxN5w-1; Tue, 14 Jun 2022 09:23:36 -0400 X-MC-Unique: cNJ9xJ4nMleKRuB2aLxN5w-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D5456185A7B2; Tue, 14 Jun 2022 13:23:35 +0000 (UTC) Received: from [10.39.208.29] (unknown [10.39.208.29]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B2860492CA4; Tue, 14 Jun 2022 13:23:33 +0000 (UTC) Message-ID: Date: Tue, 14 Jun 2022 15:23:30 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 To: Yuan Wang , chenbo.xia@intel.com, dev@dpdk.org Cc: jiayu.hu@intel.com, xuan.ding@intel.com, sunil.pai.g@intel.com References: <20220413182742.860659-1-yuanx.wang@intel.com> <20220609173404.1769210-1-yuanx.wang@intel.com> <20220609173404.1769210-2-yuanx.wang@intel.com> From: Maxime Coquelin Subject: Re: [PATCH v5 1/2] vhost: support clear in-flight packets for async dequeue In-Reply-To: <20220609173404.1769210-2-yuanx.wang@intel.com> X-Scanned-By: MIMEDefang 2.85 on 10.11.54.9 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/9/22 19:34, Yuan Wang wrote: > rte_vhost_clear_queue_thread_unsafe() supports to clear > in-flight packets for async enqueue only. But after > supporting async dequeue, this API should support async dequeue too. > > This patch also adds the thread-safe version of this API, > the difference between the two API is that thread safety uses lock. > > These APIs maybe used to clean up packets in the async channel > to prevent packet loss when the device state changes or > when the device is destroyed. > > Signed-off-by: Yuan Wang > --- > doc/guides/prog_guide/vhost_lib.rst | 8 ++- > doc/guides/rel_notes/release_22_07.rst | 4 ++ > lib/vhost/rte_vhost_async.h | 25 +++++++ > lib/vhost/version.map | 1 + > lib/vhost/virtio_net.c | 93 +++++++++++++++++++++++++- > 5 files changed, 128 insertions(+), 3 deletions(-) > Reviewed-by: Maxime Coquelin Thanks, Maxime