From: Gregory Etelson <getelson@nvidia.com>
To: <dev@dpdk.org>
Cc: <getelson@nvidia.com>, <matan@nvidia.com>, <rasland@nvidia.com>,
<orika@nvidia.com>, Ray Kinsella <mdr@ashroe.eu>
Subject: [dpdk-dev] [PATCH] net: announce changes in IPv4 header
Date: Mon, 2 Aug 2021 13:38:34 +0300 [thread overview]
Message-ID: <20210802103834.14263-1-getelson@nvidia.com> (raw)
Announce changes to add 2 unions. The first union will provide
integral and bits access to version and IHL. The second union will
provide integral and bits access to fragment flags and offset.
Signed-off-by: Gregory Etelson <getelson@nvidia.com>
---
doc/guides/rel_notes/deprecation.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index d9c0e65921..46f8a10dc5 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -158,3 +158,8 @@ Deprecation Notices
* security: The functions ``rte_security_set_pkt_metadata`` and
``rte_security_get_userdata`` will be made inline functions and additional
flags will be added in structure ``rte_security_ctx`` in DPDK 21.11.
+
+* net: The structure ``rte_ipv4_hdr`` will have two unions.
+ The first union is for existing ``version_ihl`` byte and new bitfield for
+ version and IHL. The second union is for existing ``fragment_offset`` and
+ new bitfield for fragment flags and offset.
--
2.32.0
next reply other threads:[~2021-08-02 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 10:38 Gregory Etelson [this message]
2021-08-02 10:42 ` Andrew Rybchenko
2021-08-02 12:10 ` Slava Ovsiienko
2021-08-02 12:38 ` Akhil Goyal
2021-08-03 18:06 ` Ajit Khaparde
2021-08-04 14:27 ` Thomas Monjalon
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=20210802103834.14263-1-getelson@nvidia.com \
--to=getelson@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=mdr@ashroe.eu \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.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;
as well as URLs for NNTP newsgroup(s).