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 41082A00C2; Fri, 6 Jan 2023 10:33:49 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2F0EF400EF; Fri, 6 Jan 2023 10:33:49 +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 519F4400D4 for ; Fri, 6 Jan 2023 10:33:47 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1672997626; 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=48V/UYJ9ViQQbLnZljXL71Us46Nun8kg0J51lWP9gOQ=; b=VuLGU5fQfdgMhgNBZ0VGJdfZjQrDsOEIDZ5WIWaI+ngAdcS9wED+uJA+lyAB8uTbA+hhw+ 0wZ978XrNOFSAa0TrO3cbJXZUZkexnjsneOEwbcIxrOWlnfU/FrDfG7AreS8bJFCx+q/2S XSdfobPZEfm8JLFy9XrQ2uSpw/qCno0= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-602-w3E0qZrcNnqV9O6LpdxW4A-1; Fri, 06 Jan 2023 04:33:43 -0500 X-MC-Unique: w3E0qZrcNnqV9O6LpdxW4A-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 418D529AA381; Fri, 6 Jan 2023 09:33:43 +0000 (UTC) Received: from [10.39.208.15] (unknown [10.39.208.15]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7ABA8492B06; Fri, 6 Jan 2023 09:33:42 +0000 (UTC) Message-ID: <9dfbb1a3-382c-8785-c1b0-c5b40470262f@redhat.com> Date: Fri, 6 Jan 2023 10:33:41 +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: [RFC] net/vhost: support asynchronous data path To: "Wang, YuanX" , "dev@dpdk.org" Cc: "Hu, Jiayu" References: <20221216020009.70206-1-yuanx.wang@intel.com> From: Maxime Coquelin In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.9 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 Hi, On 1/6/23 10:08, Wang, YuanX wrote: > Hi Maxime, > > Sorry about not being clear about the intentions. > The patch is for a whitepaper, we use it for tests and we need to attach the patch link. Thanks for the clarification. > Maybe I should set the patch state to superseded? I think setting it to rejected would be the appropriate state, as there are no patch that supersedes it. Thanks, Maxime > Thanks, > Yuan > >> -----Original Message----- >> From: Maxime Coquelin >> Sent: Monday, January 2, 2023 6:59 PM >> To: Wang, YuanX ; dev@dpdk.org >> Cc: Hu, Jiayu >> Subject: Re: [RFC] net/vhost: support asynchronous data path >> >> Hi Yuan, >> >> On 12/16/22 03:00, Yuan Wang wrote: >>> Vhost asynchronous data-path offloads packet copy from the CPU to the >>> DMA engine. As a result, large packet copy can be accelerated by the >>> DMA engine, and vhost can free CPU cycles for higher level functions. >>> >>> In this patch, we enable asynchronous data-path for vhostpmd. >>> Asynchronous data path is enabled per tx/rx queue, and users need to >>> specify the DMA device used by the tx/rx queue. Each tx/rx queue only >>> supports to use one DMA device, but one DMA device can be shared >> among >>> multiple tx/rx queues of different vhost PMD ports. >>> >>> Two PMD parameters are added: >>> - dmas: specify the used DMA device for a tx/rx queue. >>> (Default: no queues enable asynchronous data path) >>> - dma-ring-size: DMA ring size. >>> (Default: 4096). >>> >>> Here is an example: >>> --vdev >> 'eth_vhost0,iface=./s0,dmas=[txq0@0000:00.01.0;rxq0@0000:00.01.1],dma- >> ring-size=4096' >>> >>> Signed-off-by: Jiayu Hu >>> Signed-off-by: Yuan Wang >>> Signed-off-by: Wenwu Ma >>> --- >>> drivers/net/vhost/meson.build | 1 + >>> drivers/net/vhost/rte_eth_vhost.c | 512 >> ++++++++++++++++++++++++++++-- >>> drivers/net/vhost/rte_eth_vhost.h | 15 + >>> drivers/net/vhost/version.map | 7 + >>> drivers/net/vhost/vhost_testpmd.c | 67 ++++ >>> 5 files changed, 569 insertions(+), 33 deletions(-) >>> create mode 100644 drivers/net/vhost/vhost_testpmd.c >>> >> >> This RFC is identical to the v5 that you sent for last release, and so the >> comments I made on it are still valid. >> >> Is this intentionally re-sent? >> >> Regards, >> Maxime >