From: Marcus Wichelmann <marcus.wichelmann@hetzner-cloud.de>
To: xdp-newbies@vger.kernel.org, cloud@xdp-project.net
Subject: [xdp-cloud] Questions about Offloads and XDP-Hints regarding a Cloud-Provider Use-Case
Date: Wed, 28 Sep 2022 15:54:03 +0200 [thread overview]
Message-ID: <30dd392b-ff2f-1e25-175a-6666dde200ed@hetzner-cloud.de> (raw)
Hello,
I'm working for a cloud hosting provider and we're working on a new
XDP-based networking stack for our VM-Hosts that uses XDP to accelerate
the connectivity of our qemu/KVM VMs to the outside.
For this, we use XDP_REDIRECT to forward packets between the physical
host NIC and the VM tap devices. The main issue we have now is, that our
VM guests have some virtio NIC offloads enabled: rx/tx checksumming,
TSO/GSO, GRO and Scatter-Gather.
Currently, these offloads (especially TSO/GSO) are incompatible with
XDP_REDIRECT and result in packets being dropped. Because disabling
these offloads in all our customer VMs is not a good option, we're
searching for ways to support these offloads with XDP.
The XDP multi-buffer support needed for TSO/GSO seems to be mostly there
already, but, to our understanding, the last missing part for full
TSO/GSO support is a way to tell the physical NIC to perform the TSO/GSO
offload.
I've seen the latest LPC 2022 talk from Jesper Dangaard Brouer
regarding the planned XDP-Hints feature. But this was mainly about
Checksum and VLAN offloads. Is supporting TSO/GSO also one of the goals
you have in mind with these XDP-Hints proposals?
Will the multi-buffer and hints patches be all what's needed to make
XDP_REDIRECT between a VM (without disabled offloads) and the host NIC
possible, or are there more things missing in XDP that will become an
issue in that use-case?
The "XDP Cloud-Provider" project page describes a very similar use-case
to what we plan to do. What's the goal of this project?
We're very interested in the work on XDP-Hints and in the performance
benefits that the offloading support could bring to XDP and I would be
thankful if you could help us with some of our questions.
Best regards,
Marcus Wichelmann
Hetzner Cloud GmbH
next reply other threads:[~2022-09-28 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 13:54 Marcus Wichelmann [this message]
2022-09-28 18:07 ` [xdp-cloud] " Jesper Dangaard Brouer
2022-09-28 18:32 ` David Ahern
[not found] ` <YzTMmGuZjiO8+dVu@lore-desk>
2022-09-29 2:14 ` Jason Wang
2022-09-29 4:00 ` David Ahern
2022-09-29 13:16 ` Marcus Wichelmann
2022-10-03 10:56 ` Jesper Dangaard Brouer
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
List information: https://lists.xdp-project.net/postorius/lists/cloud.xdp-project.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30dd392b-ff2f-1e25-175a-6666dde200ed@hetzner-cloud.de \
--to=marcus.wichelmann@hetzner-cloud.de \
--cc=cloud@xdp-project.net \
--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