From: Serhii Iliushyk <sil-plv@napatech.com>
To: dev@dpdk.org
Cc: mko-plv@napatech.com, sil-plv@napatech.com, ckm@napatech.com,
andrew.rybchenko@oktetlabs.ru, ferruh.yigit@amd.com,
stephen@networkplumber.org,
Danylo Vodopianov <dvo-plv@napatech.com>
Subject: [PATCH v1 1/3] net/ntnic: fix action modify field DSCP
Date: Wed, 20 Nov 2024 19:02:55 +0100 [thread overview]
Message-ID: <20241120180258.64185-2-sil-plv@napatech.com> (raw)
In-Reply-To: <20241120180258.64185-1-sil-plv@napatech.com>
From: Danylo Vodopianov <dvo-plv@napatech.com>
The issue with modification of the DSCP field
for IPV4 and IPV6 is fixed by adding
copying the DSCP value to the flow handler.
Fixes: 6fec9a9a12e1 ("net/ntnic: add infrastructure for flow actions and items")
Signed-off-by: Danylo Vodopianov <dvo-plv@napatech.com>
---
.../nthw/flow_api/profile_inline/flow_api_profile_inline.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/net/ntnic/nthw/flow_api/profile_inline/flow_api_profile_inline.c b/drivers/net/ntnic/nthw/flow_api/profile_inline/flow_api_profile_inline.c
index a34839e00c..683610445d 100644
--- a/drivers/net/ntnic/nthw/flow_api/profile_inline/flow_api_profile_inline.c
+++ b/drivers/net/ntnic/nthw/flow_api/profile_inline/flow_api_profile_inline.c
@@ -3057,6 +3057,10 @@ static void copy_fd_to_fh_flm(struct flow_handle *fh, const struct nic_flow_def
for (unsigned int i = 0; i < fd->modify_field_count; ++i) {
switch (fd->modify_field[i].select) {
case CPY_SELECT_DSCP_IPV4:
+ case CPY_SELECT_DSCP_IPV6:
+ fh->flm_dscp = fd->modify_field[i].value8[0];
+ break;
+
case CPY_SELECT_RQI_QFI:
fh->flm_rqi = (fd->modify_field[i].value8[0] >> 6) & 0x1;
fh->flm_qfi = fd->modify_field[i].value8[0] & 0x3f;
--
2.45.0
next prev parent reply other threads:[~2024-11-20 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 18:02 [PATCH v1 0/3] Bugfixes Serhii Iliushyk
2024-11-20 18:02 ` Serhii Iliushyk [this message]
2024-11-20 18:02 ` [PATCH v1 2/3] net/ntnic: add supplementary macros Serhii Iliushyk
2024-11-20 18:02 ` [PATCH v1 3/3] net/ntnic: move headers to driver's root Serhii Iliushyk
2024-11-24 18:12 ` [PATCH v1 0/3] Bugfixes Stephen Hemminger
2024-11-25 10:27 ` Serhii Iliushyk
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=20241120180258.64185-2-sil-plv@napatech.com \
--to=sil-plv@napatech.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=ckm@napatech.com \
--cc=dev@dpdk.org \
--cc=dvo-plv@napatech.com \
--cc=ferruh.yigit@amd.com \
--cc=mko-plv@napatech.com \
--cc=stephen@networkplumber.org \
/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).