From: Hyong Youb Kim <hyonkim@cisco.com>
To: dev@dpdk.org
Cc: johndale@cisco.com, Hyong Youb Kim <hyonkim@cisco.com>,
adrien.mazarguil@6wind.com
Subject: [dpdk-dev] [PATCH] net/enic: fix flow drop action
Date: Thu, 10 May 2018 01:51:13 -0700 [thread overview]
Message-ID: <20180510085113.14666-1-hyonkim@cisco.com> (raw)
Drop is a fate-deciding action, so mark it as FATE. It was missing in
a previous commit.
Fixes: cc17feb90413 ("ethdev: alter behavior of flow API actions")
Signed-off-by: Hyong Youb Kim <hyonkim@cisco.com>
Cc: adrien.mazarguil@6wind.com
---
drivers/net/enic/enic_flow.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/net/enic/enic_flow.c b/drivers/net/enic/enic_flow.c
index 525f3dd7c..0cf04aefd 100644
--- a/drivers/net/enic/enic_flow.c
+++ b/drivers/net/enic/enic_flow.c
@@ -1062,6 +1062,9 @@ enic_copy_action_v2(const struct rte_flow_action actions[],
break;
}
case RTE_FLOW_ACTION_TYPE_DROP: {
+ if (overlap & FATE)
+ return ENOTSUP;
+ overlap |= FATE;
enic_action->flags |= FILTER_ACTION_DROP_FLAG;
break;
}
--
2.16.2
next reply other threads:[~2018-05-10 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 8:51 Hyong Youb Kim [this message]
2018-05-10 23:04 ` 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=20180510085113.14666-1-hyonkim@cisco.com \
--to=hyonkim@cisco.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=johndale@cisco.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).