From: Artemii Morozov <artemii.morozov@arknetworks.am>
To: dev@dpdk.org
Cc: Ivan Malov <ivan.malov@arknetworks.am>,
Viacheslav Galaktionov <viacheslav.galaktionov@arknetworks.am>,
Andy Moreton <amoreton@xilinx.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: [PATCH 1/2] common/sfc_efx/base: add MAE IP fragmentation match bits
Date: Fri, 23 Jun 2023 20:58:23 +0400 [thread overview]
Message-ID: <20230623165824.51908-2-artemii.morozov@arknetworks.am> (raw)
In-Reply-To: <20230623165824.51908-1-artemii.morozov@arknetworks.am>
Introduce necessary infrastructure for these bits to
be set and validated. Using a combination of these bits
IP fragmentation can be configured.
Signed-off-by: Artemii Morozov <artemii.morozov@arknetworks.am>
Reviewed-by: Ivan Malov <ivan.malov@arknetworks.am>
Reviewed-by: Andy Moreton <amoreton@xilinx.com>
---
drivers/common/sfc_efx/base/efx.h | 4 ++++
drivers/common/sfc_efx/base/efx_mae.c | 4 ++++
2 files changed, 8 insertions(+)
diff --git a/drivers/common/sfc_efx/base/efx.h b/drivers/common/sfc_efx/base/efx.h
index 77f855bfb0..efefea717f 100644
--- a/drivers/common/sfc_efx/base/efx.h
+++ b/drivers/common/sfc_efx/base/efx.h
@@ -4317,6 +4317,10 @@ typedef enum efx_mae_field_id_e {
*/
EFX_MAE_FIELD_RECIRC_ID,
EFX_MAE_FIELD_CT_MARK,
+
+ /* Single bits which can be set by efx_mae_match_spec_bit_set(). */
+ EFX_MAE_FIELD_IS_IP_FRAG,
+ EFX_MAE_FIELD_IP_FIRST_FRAG,
EFX_MAE_FIELD_NIDS
} efx_mae_field_id_t;
diff --git a/drivers/common/sfc_efx/base/efx_mae.c b/drivers/common/sfc_efx/base/efx_mae.c
index 9ff887e04b..d36cdc71be 100644
--- a/drivers/common/sfc_efx/base/efx_mae.c
+++ b/drivers/common/sfc_efx/base/efx_mae.c
@@ -483,6 +483,8 @@ typedef enum efx_mae_field_cap_id_e {
EFX_MAE_FIELD_ID_ENC_HAS_IVLAN = MAE_FIELD_ENC_HAS_IVLAN,
EFX_MAE_FIELD_ID_RECIRC_ID = MAE_FIELD_RECIRC_ID,
EFX_MAE_FIELD_ID_CT_MARK = MAE_FIELD_CT_MARK,
+ EFX_MAE_FIELD_ID_IS_IP_FRAG = MAE_FIELD_IS_IP_FRAG,
+ EFX_MAE_FIELD_ID_IP_FIRST_FRAG = MAE_FIELD_IP_FIRST_FRAG,
EFX_MAE_FIELD_CAP_NIDS
} efx_mae_field_cap_id_t;
@@ -668,6 +670,8 @@ static const efx_mae_mv_bit_desc_t __efx_mae_action_rule_mv_bit_desc_set[] = {
EFX_MAE_MV_BIT_DESC(HAS_IVLAN),
EFX_MAE_MV_BIT_DESC(ENC_HAS_OVLAN),
EFX_MAE_MV_BIT_DESC(ENC_HAS_IVLAN),
+ EFX_MAE_MV_BIT_DESC(IS_IP_FRAG),
+ EFX_MAE_MV_BIT_DESC(IP_FIRST_FRAG),
#undef EFX_MAE_MV_BIT_DESC
};
--
2.34.1
next prev parent reply other threads:[~2023-06-23 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 16:58 [PATCH 0/2] support IPv4 fragment matching in transfer rules Artemii Morozov
2023-06-23 16:58 ` Artemii Morozov [this message]
2023-06-23 16:58 ` [PATCH 2/2] net/sfc: " Artemii Morozov
2023-06-27 14:02 ` [PATCH 0/2] " Ferruh Yigit
2023-06-28 7:00 ` [PATCH v2 " Artemii Morozov
2023-06-28 7:00 ` [PATCH v2 1/2] common/sfc_efx/base: add MAE IP fragmentation match bits Artemii Morozov
2023-06-28 7:00 ` [PATCH v2 2/2] net/sfc: support IPv4 fragment matching in transfer rules Artemii Morozov
2023-06-28 10:53 ` [PATCH v2 0/2] " Ferruh Yigit
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=20230623165824.51908-2-artemii.morozov@arknetworks.am \
--to=artemii.morozov@arknetworks.am \
--cc=amoreton@xilinx.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=ivan.malov@arknetworks.am \
--cc=viacheslav.galaktionov@arknetworks.am \
/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).