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 A39CFA0544; Wed, 15 Jun 2022 01:57:06 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9499C410D3; Wed, 15 Jun 2022 01:57:06 +0200 (CEST) Received: from mga06.intel.com (mga06b.intel.com [134.134.136.31]) by mails.dpdk.org (Postfix) with ESMTP id 28BE640220 for ; Wed, 15 Jun 2022 01:57:04 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1655251025; x=1686787025; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=OOPSdsBozJR8aO9bc8SOfKBeNkxYGsN4Z30dQWdhKsU=; b=FyYHiiPRhEVY1fr3QeCdgyyuI9+gLb9vJNADwQ9Bb5aRijEyScAwF/Mc Bg6BBshk66s/yCCtNTfYwMYnb2WODvqttfLQ8wpUojoih5dkf3Kxu7hz5 vymo81LK+J02izpU0R7AW9VszDIHkqxrd/NXxuG2sakN9QyooTfrgxUmj G+mo7+esiPGuMct9dKJuhh51yWP9zlJEflSvS4PeKxM87Qj6RI0tQq3AN pgWcu0TloOhI2iQDufBVZ65VjI0kueGo4SGMuU2lapvzynD7KhPHPddWo wAJ3K+GFd6KB8nl6wqKUV80d3+5mBwkuUrbptoq3+eeVH5vgks5ofyUqf Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10378"; a="340440031" X-IronPort-AV: E=Sophos;i="5.91,300,1647327600"; d="scan'208";a="340440031" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Jun 2022 16:57:03 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.91,300,1647327600"; d="scan'208";a="727080067" Received: from fmsmsx601.amr.corp.intel.com ([10.18.126.81]) by fmsmga001.fm.intel.com with ESMTP; 14 Jun 2022 16:57:03 -0700 Received: from fmsmsx611.amr.corp.intel.com (10.18.126.91) by fmsmsx601.amr.corp.intel.com (10.18.126.81) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.27; Tue, 14 Jun 2022 16:57:02 -0700 Received: from fmsmsx612.amr.corp.intel.com (10.18.126.92) by fmsmsx611.amr.corp.intel.com (10.18.126.91) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.27; Tue, 14 Jun 2022 16:56:08 -0700 Received: from fmsmsx612.amr.corp.intel.com ([10.18.126.92]) by fmsmsx612.amr.corp.intel.com ([10.18.126.92]) with mapi id 15.01.2308.027; Tue, 14 Jun 2022 16:56:08 -0700 From: "Hu, Jiayu" To: "Wang, YuanX" , "maxime.coquelin@redhat.com" , "Xia, Chenbo" , "dev@dpdk.org" CC: "Ding, Xuan" , "Pai G, Sunil" Subject: RE: [PATCH v5 1/2] vhost: support clear in-flight packets for async dequeue Thread-Topic: [PATCH v5 1/2] vhost: support clear in-flight packets for async dequeue Thread-Index: AQHYe+W6RhrcaVPV9EWOHCJenl+QpK1PnFpQ Date: Tue, 14 Jun 2022 23:56:05 +0000 Message-ID: <779f2e1bde854131943b0a5fbaadc1c7@intel.com> References: <20220413182742.860659-1-yuanx.wang@intel.com> <20220609173404.1769210-1-yuanx.wang@intel.com> <20220609173404.1769210-2-yuanx.wang@intel.com> In-Reply-To: <20220609173404.1769210-2-yuanx.wang@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-reaction: no-action dlp-version: 11.6.500.17 dlp-product: dlpe-windows x-originating-ip: [10.239.127.36] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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 > -----Original Message----- > From: Wang, YuanX > Sent: Friday, June 10, 2022 1:34 AM > To: maxime.coquelin@redhat.com; Xia, Chenbo ; > dev@dpdk.org > Cc: Hu, Jiayu ; Ding, Xuan ; Pai > G, Sunil ; Wang, YuanX > Subject: [PATCH v5 1/2] vhost: support clear in-flight packets for async > dequeue >=20 > rte_vhost_clear_queue_thread_unsafe() supports to clear in-flight packets > for async enqueue only. But after supporting async dequeue, this API shou= ld > support async dequeue too. >=20 > This patch also adds the thread-safe version of this API, the difference > between the two API is that thread safety uses lock. >=20 > 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= . >=20 > 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(-) >=20 Reviewed-by: Jiayu Hu Thanks, Jiayu