From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: David Marchand <david.marchand@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: tap device speed
Date: Wed, 4 Oct 2023 09:08:29 +0200 [thread overview]
Message-ID: <a218ec57-2640-40d0-b9f1-b414dc3c9ef4@redhat.com> (raw)
In-Reply-To: <CAJFAV8xZv_R5Wum9NS5+ggq=tnjk12KHueh0UtrCnxFVww58Cg@mail.gmail.com>
On 10/4/23 08:17, David Marchand wrote:
> On Tue, Oct 3, 2023 at 6:01 PM Stephen Hemminger
> <stephen@networkplumber.org> wrote:
>>
>> On Tue, 3 Oct 2023 10:49:16 +0200
>> Antonio Di Bacco <a.dibacco.ks@gmail.com> 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
next prev parent reply other threads:[~2023-10-04 7:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 19:13 Antonio Di Bacco
2023-10-02 21:21 ` Stephen Hemminger
2023-10-03 8:49 ` Antonio Di Bacco
2023-10-03 16:01 ` Stephen Hemminger
2023-10-04 6:17 ` David Marchand
2023-10-04 7:08 ` Maxime Coquelin [this message]
2023-10-04 7:42 ` Antonio Di Bacco
2023-10-04 7:49 ` Maxime Coquelin
2023-10-09 17:48 ` Antonio Di Bacco
2023-10-09 18:42 ` Maxime Coquelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a218ec57-2640-40d0-b9f1-b414dc3c9ef4@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=a.dibacco.ks@gmail.com \
--cc=david.marchand@redhat.com \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).