DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Robin Jarry" <rjarry@redhat.com>,
	"David Marchand" <david.marchand@redhat.com>, <dev@dpdk.org>
Cc: "Stephen Hemminger" <stephen@networkplumber.org>,
	"Chengwen Feng" <fengchengwen@huawei.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>
Subject: RE: [PATCH] net: fix IPv4 cksum simple function
Date: Tue, 5 Nov 2024 10:53:15 +0100	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F878@smartserver.smartshare.dk> (raw)
In-Reply-To: <D5E56W7YRO4Z.367Z4JX4MFH16@redhat.com>

> From: Robin Jarry [mailto:rjarry@redhat.com]
> Sent: Tuesday, 5 November 2024 10.37
> 
> Morten Brørup, Nov 05, 2024 at 10:09:
> > For consistency, could one of you - David or Robin - please also
> > 2-byte align the IPv6 header structure?
> 
> I can send a patch but I wonder if this is really necessary after the
> RC-1 has passed?

Yes, please.
And don't forget the extension headers (rte_ipv6_routing_ext and rte_ipv6_fragment_ext).

> 
> We don't have any gcc warning related to IPv6 unaligned access (except
> maybe in drivers).

I think both IPv4 and IPv6 headers are always 2-byte aligned IRL; so for consistency and to prevent potential future problems, the API should reflect this.

Consistency is important: If the alignment differs between IPv4 and IPv6 headers in the API, someone might think there is a good reason for this, and as time passes no one will be able to answer why there is a difference.

PS:
I am also pushing for 2-byte aligning Layer 4 headers (TCP, UDP, etc.), e.g. for checksumming purposes; but didn't get enough response to that RFC:
https://inbox.dpdk.org/dev/20241011160653.88028-1-mb@smartsharesystems.com/


  reply	other threads:[~2024-11-05  9:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05  8:59 David Marchand
2024-11-05  9:09 ` Morten Brørup
2024-11-05  9:27   ` David Marchand
2024-11-05 10:20     ` Morten Brørup
2024-11-05 10:49       ` David Marchand
2024-11-05 11:02         ` Bruce Richardson
2024-11-05 11:06           ` Morten Brørup
2024-11-05 13:12           ` David Marchand
2024-11-05  9:37   ` Robin Jarry
2024-11-05  9:53     ` Morten Brørup [this message]
2024-11-06 20:22   ` David Marchand
2024-11-05 10:18 ` Bruce Richardson

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=98CBD80474FA8B44BF855DF32C47DC35E9F878@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=rjarry@redhat.com \
    --cc=stephen@networkplumber.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).