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 4FDB3426B6 for ; Wed, 4 Oct 2023 09:08:37 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 179BC4029A; Wed, 4 Oct 2023 09:08:37 +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 8453740289 for ; Wed, 4 Oct 2023 09:08:35 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1696403315; 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=6CztFa9SBkS8HsOHfQJaeLCydnlGUGk+WDMmlctaLA8=; b=Y4pVQJkAAdb4LQIC0Qs8Dic882+SC1OKoaUiPzZGKAo94QfDkZy/jCiGFWTxbMMyWTZKM+ wnDgQq6T0/o4bP5VZBgLyqbUUdOncipVgSrIejqRxn34O1VbLO6X1RNR0Q2IyILqtSmjuR 1LF3sM7uDk5O7XeqPXYrmXKoShyx4J4= 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-270-Q34kdlskMnOBbMl7cBsq_w-1; Wed, 04 Oct 2023 03:08:32 -0400 X-MC-Unique: Q34kdlskMnOBbMl7cBsq_w-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (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 B59BC858F1D; Wed, 4 Oct 2023 07:08:31 +0000 (UTC) Received: from [10.39.208.4] (unknown [10.39.208.4]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D5A762026D68; Wed, 4 Oct 2023 07:08:30 +0000 (UTC) Message-ID: Date: Wed, 4 Oct 2023 09:08:29 +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: David Marchand , Stephen Hemminger , Antonio Di Bacco Cc: users@dpdk.org References: <20231002142133.27590624@hermes.local> <20231003090112.77cd1d2c@hermes.local> From: Maxime Coquelin In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.4 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 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