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 6CD0742928; Wed, 12 Apr 2023 17:28:17 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 51147410F3; Wed, 12 Apr 2023 17:28:17 +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 75669406A2 for ; Wed, 12 Apr 2023 17:28:15 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1681313295; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ZvkjRqQ25g0hawvv71HuwK3pEb5CQTBWjoYx5gYVxBA=; b=F/1g3pu0Ai+5LPY26cQwW6cyRNnKWzHOT86bmWrZTN9/Cuu0jZ/2l+UbkySM5zoE+M6lq7 Ay7KG4zf2CceRYHdIBYq186T52SuX9VuXOmluvt+Wr1qLPesEzmkX3TQHUvEU2bWbLXl4l wdiSWUBE803FwD5v7s5bZ/KK9sSwgOY= 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-279-gQ_WNwv6NtaDlahB5XkIKQ-1; Wed, 12 Apr 2023 11:28:12 -0400 X-MC-Unique: gQ_WNwv6NtaDlahB5XkIKQ-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 93CC8857FB2; Wed, 12 Apr 2023 15:28:11 +0000 (UTC) Received: from [10.39.208.7] (unknown [10.39.208.7]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2038840C845F; Wed, 12 Apr 2023 15:28:08 +0000 (UTC) Message-ID: <107f53d8-c0c3-68a8-1857-4b6ef0165b48@redhat.com> Date: Wed, 12 Apr 2023 17:28:07 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [RFC 00/27] Add VDUSE support to Vhost library To: Ferruh Yigit , dev@dpdk.org, david.marchand@redhat.com, chenbo.xia@intel.com, mkp@redhat.com, fbl@redhat.com, jasowang@redhat.com, cunming.liang@intel.com, xieyongji@bytedance.com, echaudro@redhat.com, eperezma@redhat.com, amorenoz@redhat.com References: <20230331154259.1447831-1-maxime.coquelin@redhat.com> <3789c0c7-281b-89c3-45aa-3d985736b04a@amd.com> From: Maxime Coquelin In-Reply-To: <3789c0c7-281b-89c3-45aa-3d985736b04a@amd.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 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 Ferruh, On 4/12/23 13:33, Ferruh Yigit wrote: > On 3/31/2023 4:42 PM, Maxime Coquelin wrote: >> This series introduces a new type of backend, VDUSE, >> to the Vhost library. >> >> VDUSE stands for vDPA device in Userspace, it enables >> implementing a Virtio device in userspace and have it >> attached to the Kernel vDPA bus. >> >> Once attached to the vDPA bus, it can be used either by >> Kernel Virtio drivers, like virtio-net in our case, via >> the virtio-vdpa driver. Doing that, the device is visible >> to the Kernel networking stack and is exposed to userspace >> as a regular netdev. >> >> It can also be exposed to userspace thanks to the >> vhost-vdpa driver, via a vhost-vdpa chardev that can be >> passed to QEMU or Virtio-user PMD. >> >> While VDUSE support is already available in upstream >> Kernel, a couple of patches are required to support >> network device type: >> >> https://gitlab.com/mcoquelin/linux/-/tree/vduse_networking_poc >> >> In order to attach the created VDUSE device to the vDPA >> bus, a recent iproute2 version containing the vdpa tool is >> required. > > Hi Maxime, > > Is this a replacement to the existing DPDK vDPA framework? What is the > plan for long term? > No, this is not a replacement for DPDK vDPA framework. We (Red Hat) don't have plans to support DPDK vDPA framework in our products, but there are still contribution to DPDK vDPA by several vDPA hardware vendors (Intel, Nvidia, Xilinx), so I don't think it is going to be deprecated soon. Regards, Maxime