From: David Marchand <david.marchand@redhat.com>
To: Gregory Etelson <getelson@nvidia.com>
Cc: "Morten Brørup" <mb@smartsharesystems.com>,
dev@dpdk.org, andrew.rybchenko@oktetlabs.ru,
bruce.richardson@intel.com, cristian.dumitrescu@intel.com,
ferruh.yigit@amd.com, jasvinder.singh@intel.com,
konstantin.v.ananyev@yandex.ru, mkashani@nvidia.com,
orika@nvidia.com, ruifeng.wang@arm.com, thomas@monjalon.net
Subject: Re: [PATCH v4] net: add bit fields to IPv6 header definition
Date: Fri, 18 Oct 2024 18:47:10 +0200 [thread overview]
Message-ID: <CAJFAV8wvD8TZ_DPH0FnhibqLc7+MJU=FaTo9J61NF3rt8D19gw@mail.gmail.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F535@smartserver.smartshare.dk>
On Tue, Jun 18, 2024 at 2:44 PM Morten Brørup <mb@smartsharesystems.com> wrote:
> > From: Gregory Etelson [mailto:getelson@nvidia.com]
> >
> > DPDK IPv6 header definition combined the `version`, `traffic class`
> > and `flow label` header fields into a single 32 bits structure member
> > `vtc_flow`.
> >
> > The patch expands IPv6 header definition with dedicated structure
> > members for the `version`, `traffic class` and `flow label` fields.
> > The `traffic class` is also separated into DS and ECN fields.
> >
> > The patch also preserves existing `vtc_flow` structure member for
> > backward compatibility.
> >
> > Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> Reviewed-by: Morten Brørup <mb@smartsharesystems.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2024-10-18 16:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 5:17 [PATCH] " Gregory Etelson
2024-06-18 6:42 ` Morten Brørup
2024-06-18 7:02 ` Morten Brørup
2024-06-18 8:07 ` Etelson, Gregory
2024-06-19 0:11 ` Tyler Retzlaff
2024-06-19 4:31 ` Etelson, Gregory
2024-06-18 7:58 ` [PATCH v2] " Gregory Etelson
2024-06-18 8:11 ` Morten Brørup
2024-06-18 9:51 ` [PATCH v3] " Gregory Etelson
2024-06-18 10:47 ` Morten Brørup
2024-06-18 12:18 ` [PATCH v4] " Gregory Etelson
2024-06-18 12:44 ` Morten Brørup
2024-10-18 16:47 ` David Marchand [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='CAJFAV8wvD8TZ_DPH0FnhibqLc7+MJU=FaTo9J61NF3rt8D19gw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=getelson@nvidia.com \
--cc=jasvinder.singh@intel.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=mb@smartsharesystems.com \
--cc=mkashani@nvidia.com \
--cc=orika@nvidia.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
/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).