public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Willem de Bruijn <willemb@google.com>
Cc: Jason Wang <jasowang@redhat.com>,
	virtio-comment@lists.linux.dev, maxime.coquelin@redhat.com,
	Eelco Chaudron <echaudro@redhat.com>,
	Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: [PATCH v6 1/2] virtio-net: define UDP tunnel segmentation offload feature
Date: Thu, 1 Aug 2024 17:34:40 +0200	[thread overview]
Message-ID: <494ee50c-eae3-41fb-9823-595ce00b0c35@redhat.com> (raw)
In-Reply-To: <CA+FuTScunTfXGzpEFEgZcv3FKSzVwSK0vhuO61a=Ui2HybTsJw@mail.gmail.com>

On 7/31/24 20:21, Willem de Bruijn wrote:
> On Wed, Jul 31, 2024 at 1:32 PM Paolo Abeni <pabeni@redhat.com> wrote:
>> What about reserving an additional bit in gso_type to specify the inner
>> network header protocol?
> 
> Similar to VIRTIO_NET_HDR_GSO_ECN?
> 
> Is that preferable over VIRTIO_NET_HDR_GSO_UDP_TUNNEL_IP4 and
> .._UDP_TUNNEL_IP6 variants?

Should be basically the same, as VIRTIO_NET_HDR_GSO_UDP_TUNNEL_IP4 
VIRTIO_NET_HDR_GSO_UDP_TUNNEL_IP6 will be 2 separate bits in gso_type, 
right?

> And to parsing just this one byte (or nibble) from packet data using
> inner_nh_offset?

I think one of the state goal is to avoid parsing. More importantly, 
accessing the inner network header content this early will cause 
possibly avoidable (or at least mitigable via prefetch) cache misses.

> If it's the best of those options, no objections from me. Definitely
> no need for a u16 if the only options are IPPROTO_IP and IPPROTO_IPV6.

Wrapping all the above I'll go for the additional bit for the inner 
network header type. If I misread something, please LMK:)

Thanks,

Paolo


  parent reply	other threads:[~2024-08-01 15:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 11:30 [PATCH v6 0/2] virtio-net: define UDP tunnel offload Paolo Abeni
2024-07-29 11:30 ` [PATCH v6 1/2] virtio-net: define UDP tunnel segmentation offload feature Paolo Abeni
2024-07-29 21:04   ` Willem de Bruijn
2024-07-29 21:36     ` Willem de Bruijn
2024-07-30  7:38       ` Paolo Abeni
2024-07-30  7:33     ` Paolo Abeni
2024-07-31  4:10       ` Jason Wang
2024-07-31  9:02         ` Paolo Abeni
2024-07-31 11:17           ` Paolo Abeni
2024-08-01  3:14           ` Jason Wang
2024-07-31 14:25         ` Willem de Bruijn
2024-07-31 17:32           ` Paolo Abeni
2024-07-31 18:21             ` Willem de Bruijn
2024-08-01  3:19               ` Jason Wang
2024-08-01 15:34               ` Paolo Abeni [this message]
2024-08-01 16:04                 ` Willem de Bruijn
2024-08-01 16:26                   ` Paolo Abeni
2024-08-01 18:04                     ` Willem de Bruijn
2024-08-02  3:30                     ` Jason Wang
2024-08-01  2:24           ` Jason Wang
2024-07-31  1:57   ` Jason Wang
2024-07-31  8:43     ` Paolo Abeni
2024-07-31  9:16       ` Paolo Abeni
2024-08-01  3:01       ` Jason Wang
2024-07-29 11:30 ` [PATCH v6 2/2] virtio-net: define UDP tunnel checksum " Paolo Abeni
2024-07-29 21:35   ` Willem de Bruijn
2024-07-30  7:52     ` Paolo Abeni

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=494ee50c-eae3-41fb-9823-595ce00b0c35@redhat.com \
    --to=pabeni@redhat.com \
    --cc=echaudro@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=virtio-comment@lists.linux.dev \
    --cc=willemb@google.com \
    /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