On 10/10/2022 7:08 AM, Chaoyong He wrote:
Add the corresponding data structure and logics, to support
the offload of IPv6 item.
Signed-off-by: Chaoyong He <chaoyong...@corigine.com>
Reviewed-by: Niklas Söderlund <niklas.soderl...@corigine.com>
---
doc/guides/nics/features/nfp.ini | 2 +
doc/guides/rel_notes/release_22_11.rst | 1 +
drivers/net/nfp/flower/nfp_flower_cmsg.h | 33 +++++++++++++++
drivers/net/nfp/nfp_flow.c | 73 +++++++++++++++++++++++++++++++-
4 files changed, 107 insertions(+), 2 deletions(-)
diff --git a/doc/guides/nics/features/nfp.ini b/doc/guides/nics/features/nfp.ini
index d4ceae0..9dff34b 100644
--- a/doc/guides/nics/features/nfp.ini
+++ b/doc/guides/nics/features/nfp.ini
@@ -29,6 +29,8 @@ Usage doc = Y
[rte_flow items]
eth = Y
ipv4 = Y
+ipv6 = Y
+ipv6_frag_ext = Y
There are 'RTE_FLOW_ITEM_TYPE_IPV6_EXT' &
'RTE_FLOW_ITEM_TYPE_IPV6_FRAG_EXT' flow item types, shouldn't code check
them before claiming the support?
Please use './devtools/check-doc-vs-code.sh' script to double check if
code and .ini file matches.
