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 35BC142340 for ; Mon, 9 Oct 2023 20:42:30 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AD8E1402CB; Mon, 9 Oct 2023 20:42:29 +0200 (CEST) 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 63559402B1 for ; Mon, 9 Oct 2023 20:42:28 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1696876947; 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=QxvWVdtspeazfwkpFql3i1vGWjHOjTHtxQzeM1rurK4=; b=V5ChTSu0tQXyFih1NlFOX9iykU+sHEevUSdXHtQL1bpSn6kRLMYr9J/aHt0Ugv06HMOpQc SuC/2GjLY+n0remwMHY9STvWO06GqPIamo9DdfN5yrJ+NEyB6u2ff24lTXpR5GHsDX2udq vd1wezbkVWHhf0LGEngkdrDOnaqg68E= Received: from mimecast-mx02.redhat.com (mx-ext.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-650-n0nOP0OlPyuiNvTT4_FuZw-1; Mon, 09 Oct 2023 14:42:24 -0400 X-MC-Unique: n0nOP0OlPyuiNvTT4_FuZw-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5EE511C2B660; Mon, 9 Oct 2023 18:42:24 +0000 (UTC) Received: from [10.39.208.30] (unknown [10.39.208.30]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 85ACD40C6EA8; Mon, 9 Oct 2023 18:42:23 +0000 (UTC) Message-ID: <1bc48922-8fe2-1523-b7b5-f67999e09f71@redhat.com> Date: Mon, 9 Oct 2023 20:42:21 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Subject: Re: tap device speed To: Antonio Di Bacco Cc: David Marchand , users@dpdk.org References: <20231002142133.27590624@hermes.local> <20231003090112.77cd1d2c@hermes.local> <8bb3d2ac-5676-3c9d-1da5-4b31f72eb143@redhat.com> From: Maxime Coquelin In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 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: 8bit X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Hi Antonio, On 10/9/23 19:48, Antonio Di Bacco wrote: > Hi Maxime, > > trying to follow the steps at the link provided: > > > sage: > ====== > > 1. Probe required Kernel modules > # modprobe vdpa > # modprobe vduse > # modprobe virtio-vdpa > > 2. Build (require vduse kernel headers to be available) > # meson build > # ninja -C build > > 3. Create a VDUSE device (vduse0) using Vhost PMD with > testpmd (with 4 queue pairs in this example) > # ./build/app/dpdk-testpmd --no-pci > --vdev=net_vhost0,iface=/dev/vduse/vduse0,queues=4 --log-level=*:9 -- > -i --txq=4 --rxq=4 > > 4. Attach the VDUSE device to the vDPA bus > # vdpa dev add name vduse0 mgmtdev vduse > > I'm stuck at step 4, with an error: > > manderwo@fetgem01:~$ sudo vdpa dev add name vduse0 mgmtdev vduse > kernel answers: Invalid argument > manderwo@fetgem01:~$ vdpa mgmtdev show > vduse: > supported_classes block > manderwo@fetgem01:~$ > > Do you know what could be wrong? I guess you don't have the kernel patches applied, a recent branch can be found on my gitlab aacount. You can find instructions here: https://gitlab.com/mcoquelin/vduse-doc/-/blob/master/SETUP.md?ref_type=heads#kernel Maxime > > Thank you in advance, > Antonio. > > On Wed, Oct 4, 2023 at 9:50 AM Maxime Coquelin > wrote: >> >> >> >> On 10/4/23 09:42, Antonio Di Bacco wrote: >>> Thank you for your info that are giving me the right heads up >>> To experiment with VDUSE and share a virtual network interface (I >>> don't have a physical NIC) between the Linux kernel and DPDK using >>> VDUSE, I'm about to follow these steps: >>> >>> Load Required Kernel Modules: >>> modprobe vduse >>> Create /dev/vdpa0 device with: >>> vdpa -d /dev/vdpa0 -n my_vdpa_driver -q queue_count >>> >>> I wonder which vdpa_driver should I use, I don't have a real NIC >>> After having this vdpa0 interface up I can run my DPDK application: >>> >>> ./my_dpdk_app --vdev "net_vdpa0,iface=/dev/vdpa0" >> >> You will use the Vhost PMD in this case (alternative is to use the Vhost >> API directly). >> >> Maybe I missed to add steps with Vhost PMD in my doc repo, I'll improve >> it but in the mean time you can refer to the steps provided in the DPDK >> VDUSE series cover letter: >> https://inbox.dpdk.org/dev/7f72500a-5317-c66d-3f36-2fd65c874b47@redhat.com/T/ >> >> Please read the vduse documentation on my gitlab repo anyways, it >> provides pointers on the missing Kernel patches (being upstreamed). >> >> Maxime >> >> >>> Regards, >>> Antonio. >>> >>> On Wed, Oct 4, 2023 at 9:08 AM Maxime Coquelin >>> wrote: >>>> >>>> >>>> >>>> On 10/4/23 08:17, David Marchand wrote: >>>>> On Tue, Oct 3, 2023 at 6:01 PM Stephen Hemminger >>>>> wrote: >>>>>> >>>>>> On Tue, 3 Oct 2023 10:49:16 +0200 >>>>>> Antonio Di Bacco wrote: >>>>>> >>>>>>> I understand, could we use another solution ? Like a memif interface >>>>>>> in DPDK and libmemif in Linux? >>>>>> >>>>>> The issue is accessing kernel networking devices. Both virtio user >>>>>> and XDP are faster for that. Memif is for doing process to process networking. >>>>> >>>>> For dpdk <-> kernel, as you are mentioning virtio-user/vhost, let me >>>>> add that there is some activity on this side, with VDUSE. >>>>> >>>>> Maxime is working on the VDUSE kernel and dpdk bits. >>>>> He gave a talk about the current status during the summit and some >>>>> performance numbers: >>>>> https://dpdksummit2023.sched.com/event/1P9xA/vduse-performance-how-fast-is-it-maxime-coquelin-red-hat >>>>> >>>>> >>>> >>>> Thanks for sharing David. >>>> I'd like just to add some more information on VDUSE if you want to >>>> experiment with VDUSE, which is still under development: >>>> https://gitlab.com/mcoquelin/vduse-doc >>>> >>>> Maxime >>>> >>> >> >