From: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
To: dev@dpdk.org
Cc: matan@mellanox.com, rasland@mellanox.com, thomas@monjalon.net,
ferruh.yigit@intel.com, jerinjacobk@gmail.com,
stephen@networkplumber.org, arybchenko@solarflare.com,
ajit.khaparde@broadcom.com, maxime.coquelin@redhat.com,
olivier.matz@6wind.com, david.marchand@redhat.com
Subject: [dpdk-dev] [PATCH] doc: announce GENEVE header options support
Date: Mon, 3 Aug 2020 12:53:20 +0000 [thread overview]
Message-ID: <1596459200-30689-1-git-send-email-viacheslavo@mellanox.com> (raw)
In order to add support of the GENEVE header variable length
options the rte_flow_item_geneve_option item will be introduced:
struct rte_flow_item_geneve_option {
rte_be16_t option_class;
uint8_t option_type:7;
uint8_t critical:1;
uint8_t length:5;
uint8_t rsvd0:3;
uint8_t data[];
};
This option (one or multiple) must follow the rte_flow_item_geneve
item and provide the pattern to match with GENEVE header option.
Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
---
doc/guides/rel_notes/deprecation.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index cd700ae..b6bdb83 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -109,6 +109,10 @@ Deprecation Notices
Existing ``rte_eth_rx_descriptor_status`` and ``rte_eth_tx_descriptor_status``
APIs can be used as replacement.
+* ethdev: in order to provide support of the GENEVE header variable length
+ options in rte_flow API the rte_flow_item_geneve_option item will be
+ introduced.
+
* ethdev: Some internal APIs for driver usage are exported in the .map file.
Now DPDK has ``__rte_internal`` marker so we can mark internal APIs and move
them to the INTERNAL block in .map. Although these APIs are internal it will
--
1.8.3.1
reply other threads:[~2020-08-03 12:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1596459200-30689-1-git-send-email-viacheslavo@mellanox.com \
--to=viacheslavo@mellanox.com \
--cc=ajit.khaparde@broadcom.com \
--cc=arybchenko@solarflare.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinjacobk@gmail.com \
--cc=matan@mellanox.com \
--cc=maxime.coquelin@redhat.com \
--cc=olivier.matz@6wind.com \
--cc=rasland@mellanox.com \
--cc=stephen@networkplumber.org \
--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).