From: Steve Yang <stevex.yang@intel.com>
To: dev@dpdk.org
Cc: Yuying.Zhang@intel.com, beilei.xing@intel.com,
qiming.yang@intel.com, qi.z.zhang@intel.com,
Steve Yang <stevex.yang@intel.com>
Subject: [PATCH v1 2/2] net/ice: fix unsupported flow rule transfer attribute
Date: Mon, 26 Dec 2022 00:37:15 +0000 [thread overview]
Message-ID: <20221226003715.615278-3-stevex.yang@intel.com> (raw)
In-Reply-To: <20221226003715.615278-1-stevex.yang@intel.com>
ice doesn't support transfer attribute of flow rule,
ignore it when validating rule attributes.
Fixes: d76116a4678f ("net/ice: add generic flow API")
Signed-off-by: Steve Yang <stevex.yang@intel.com>
---
drivers/net/ice/ice_generic_flow.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/net/ice/ice_generic_flow.c b/drivers/net/ice/ice_generic_flow.c
index d496c28dec..86a32f8cb1 100644
--- a/drivers/net/ice/ice_generic_flow.c
+++ b/drivers/net/ice/ice_generic_flow.c
@@ -2030,6 +2030,14 @@ ice_flow_valid_attr(struct ice_adapter *ad,
return -rte_errno;
}
+ /* Not supported */
+ if (attr->transfer) {
+ rte_flow_error_set(error, EINVAL,
+ RTE_FLOW_ERROR_TYPE_ATTR_TRANSFER,
+ attr, "Not support transfer.");
+ return -rte_errno;
+ }
+
/* Check pipeline mode support to set classification stage */
if (ad->devargs.pipe_mode_support) {
if (attr->priority == 0)
--
2.25.1
next prev parent reply other threads:[~2022-12-26 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 0:37 [PATCH v1 0/2] " Steve Yang
2022-12-26 0:37 ` [PATCH v1 1/2] net/i40e: " Steve Yang
2023-01-17 1:26 ` Zhang, Qi Z
2023-01-17 1:26 ` Zhang, Qi Z
2022-12-26 0:37 ` Steve Yang [this message]
2023-01-17 1:29 ` [PATCH v1 2/2] net/ice: " Zhang, Qi Z
2022-12-26 1:22 ` [PATCH v1 0/2] " Yang, Qiming
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=20221226003715.615278-3-stevex.yang@intel.com \
--to=stevex.yang@intel.com \
--cc=Yuying.Zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
/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).