From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
Chaoyong He <chaoyong.he@corigine.com>,
stable@dpdk.org
Subject: [PATCH] net/nfp: fix the VLAN push flow action
Date: Fri, 12 May 2023 10:03:46 +0800 [thread overview]
Message-ID: <20230512020346.616180-1-chaoyong.he@corigine.com> (raw)
When process VLAN push flow action, the former logic perform the
mask and shift operations directly on the big endian data, which
cause both the pcp and VLAN id are not correct for offloaded packets.
Fix it by convert the data from big endian to CPU endian before
perform the mask and shift operations.
Fixes: eb9277cb2fd1 ("net/nfp: support VLAN push flow action")
Cc: stable@dpdk.org
Signed-off-by: Chaoyong He <chaoyong.he@corigine.com>
Reviewed-by: Niklas Söderlund <niklas.soderlund@corigine.com>
---
drivers/net/nfp/nfp_flow.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/net/nfp/nfp_flow.c b/drivers/net/nfp/nfp_flow.c
index 41b722f4d8..fdf5c0f40e 100644
--- a/drivers/net/nfp/nfp_flow.c
+++ b/drivers/net/nfp/nfp_flow.c
@@ -2205,6 +2205,8 @@ static int
nfp_flow_action_push_vlan(char *act_data,
const struct rte_flow_action *action)
{
+ uint8_t pcp;
+ uint16_t vid;
size_t act_size;
struct nfp_fl_act_push_vlan *push_vlan;
const struct rte_flow_action_of_push_vlan *push_vlan_conf;
@@ -2227,9 +2229,11 @@ nfp_flow_action_push_vlan(char *act_data,
(action + 1)->conf;
vlan_vid_conf = (const struct rte_flow_action_of_set_vlan_vid *)
(action + 2)->conf;
+
+ vid = rte_be_to_cpu_16(vlan_vid_conf->vlan_vid) & 0x0fff;
+ pcp = vlan_pcp_conf->vlan_pcp & 0x07;
push_vlan->vlan_tpid = push_vlan_conf->ethertype;
- push_vlan->vlan_tci = ((vlan_pcp_conf->vlan_pcp & 0x07) << 13) |
- (vlan_vid_conf->vlan_vid & 0x0fff);
+ push_vlan->vlan_tci = rte_cpu_to_be_16(vid | (pcp << 13));
return 0;
}
--
2.39.1
next reply other threads:[~2023-05-12 2:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 2:03 Chaoyong He [this message]
2023-05-18 10:12 ` 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=20230512020346.616180-1-chaoyong.he@corigine.com \
--to=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.com \
--cc=stable@dpdk.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).