All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@kernel.org>
To: Jason Wang <jasowang@redhat.com>,
	Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Jesper Dangaard Brouer <jbrouer@redhat.com>,
	Marcus Wichelmann <marcus.wichelmann@hetzner-cloud.de>,
	xdp-newbies@vger.kernel.org, cloud@xdp-project.net,
	brouer@redhat.com, Anton Protopopov <aspsk@isovalent.com>,
	Kumar Kartikeya Dwivedi <memxor@gmail.com>,
	"Karlsson, Magnus" <magnus.karlsson@intel.com>
Subject: Re: [xdp-cloud] Questions about Offloads and XDP-Hints regarding a Cloud-Provider Use-Case
Date: Wed, 28 Sep 2022 22:00:13 -0600	[thread overview]
Message-ID: <ee7fff23-17fb-810f-d532-64d74fb477c8@kernel.org> (raw)
In-Reply-To: <CACGkMEuzJ_gupygHkdmuDkH-upgTjea6rucwt0z97LHLMfsCew@mail.gmail.com>

On 9/28/22 7:14 PM, Jason Wang wrote:
> How about other metadata like gso_type, gso_segs, csum_start and
> csum_offset etc? This looks like a must for GSO to work even if
> multi-buffer is supported.

XDP redirect on Rx, packet by packet, only needs checksum valid data.

Tx and GSO is a much bigger problem.

  reply	other threads:[~2022-09-29  4:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 13:54 Questions about Offloads and XDP-Hints regarding a Cloud-Provider Use-Case Marcus Wichelmann
2022-09-28 18:07 ` [xdp-cloud] " Jesper Dangaard Brouer
2022-09-28 18:32   ` David Ahern
2022-09-28 22:37     ` Lorenzo Bianconi
2022-09-29  2:14       ` Jason Wang
2022-09-29  4:00         ` David Ahern [this message]
2022-09-29 13:16   ` [xdp-cloud] " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ee7fff23-17fb-810f-d532-64d74fb477c8@kernel.org \
    --to=dsahern@kernel.org \
    --cc=aspsk@isovalent.com \
    --cc=brouer@redhat.com \
    --cc=cloud@xdp-project.net \
    --cc=jasowang@redhat.com \
    --cc=jbrouer@redhat.com \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=magnus.karlsson@intel.com \
    --cc=marcus.wichelmann@hetzner-cloud.de \
    --cc=memxor@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.