From: David Ahern <dsahern@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Jesper Dangaard Brouer <brouer@redhat.com>
Cc: "xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org>,
David Ahern <dsahern@kernel.org>,
Anton Protopopov <aspsk2@gmail.com>
Subject: Re: Using XDP for Cloud VMs by David Ahern
Date: Mon, 24 Aug 2020 18:34:09 -0600 [thread overview]
Message-ID: <3251d735-9893-d092-e749-1fa3ef210d99@gmail.com> (raw)
In-Reply-To: <20200824171418.1b2cffa0@hermes.lan>
On 8/24/20 6:14 PM, Stephen Hemminger wrote:
> On Fri, 21 Aug 2020 11:56:14 +0200
> Jesper Dangaard Brouer <brouer@redhat.com> wrote:
>
>> is measured read [Blogpost#1]. He have even released the [Code] on GitHub,
>> and encourage people to reproduce his results.
>>
>> I encourage other cloud providers to collaborate with Ahern. XDP is a core
>> kernel building block, but we need to create FOSS projects that explore
>> different use-case (e.g xdp-cloud-provider). XDP is still early days, and as
>> Ahern already discovered, trying out this Cloud-VMs use-case have identified
>> several gotchas and missing XDP features that we should work on
>> adding/fixing in upstream kernels.
>>
>> --
>
> Was this normal OVS (kernel based) or OVS-DPDK (userspace).
> OVS-DPDK is much faster if you can afford to burn CPU.
It is not always about fastest; resource consumption on a host matters
as well. The investigation was focused on CPU cycles to process a packet
load. With kernel based OVS, you are sacrificing ~1 core (2 hardware
threads) per ~1M pps.
>
> Also would be interesting to compare XDP vs VPP but this is very much
> an apples to orange kind of exercise.
>
Endless interesting comparisons. People with the relevant knowledge and
setups will need to step up and do the tests. The source code and
scripts are available so others can do these comparisons.
prev parent reply other threads:[~2020-08-25 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 9:56 Using XDP for Cloud VMs by David Ahern Jesper Dangaard Brouer
2020-08-21 23:37 ` David Ahern
2020-08-25 0:14 ` Stephen Hemminger
2020-08-25 0:34 ` David Ahern [this message]
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=3251d735-9893-d092-e749-1fa3ef210d99@gmail.com \
--to=dsahern@gmail.com \
--cc=aspsk2@gmail.com \
--cc=brouer@redhat.com \
--cc=dsahern@kernel.org \
--cc=stephen@networkplumber.org \
--cc=xdp-newbies@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).