From: Ori Kam <orika@nvidia.com>
To: "wenjing.qiao@intel.com" <wenjing.qiao@intel.com>
Cc: "qi.z.zhang@intel.com" <qi.z.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"cristian.dumitrescu@intel.com" <cristian.dumitrescu@intel.com>
Subject: RE: [PATCH] ethdev: fix flow API support for P4-programmable devices
Date: Sun, 29 Oct 2023 07:17:37 +0000 [thread overview]
Message-ID: <MW2PR12MB466626AA060460A0ACEC8B2FD6A2A@MW2PR12MB4666.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20231027091742.3755532-1-wenjing.qiao@intel.com>
Hi Wenjing,
> -----Original Message-----
> From: wenjing.qiao@intel.com <wenjing.qiao@intel.com>
> Sent: Friday, October 27, 2023 12:18 PM
>
> From: Wenjing Qiao <wenjing.qiao@intel.com>
>
> "program" action should also be added in structure rte_flow_desc_action.
>
> Fixes: 8f1953f1914d ("ethdev: add flow API for P4-programmable devices")
>
> Signed-off-by: Wenjing Qiao <wenjing.qiao@intel.com>
> ---
> lib/ethdev/rte_flow.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/lib/ethdev/rte_flow.c b/lib/ethdev/rte_flow.c
> index 3a67f1aaba..4d6c28ee0e 100644
> --- a/lib/ethdev/rte_flow.c
> +++ b/lib/ethdev/rte_flow.c
> @@ -267,6 +267,8 @@ static const struct rte_flow_desc_data
> rte_flow_desc_action[] = {
> MK_FLOW_ACTION(IPV6_EXT_REMOVE, sizeof(struct
> rte_flow_action_ipv6_ext_remove)),
> MK_FLOW_ACTION(INDIRECT_LIST,
> sizeof(struct rte_flow_action_indirect_list)),
> + MK_FLOW_ACTION(PROG,
> + sizeof(struct rte_flow_action_prog)),
> };
>
> int
> --
> 2.34.1
Acked-by: Ori Kam <orika@nvidia.com>
Best,
Ori
next prev parent reply other threads:[~2023-10-29 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 9:17 wenjing.qiao
2023-10-29 7:17 ` Ori Kam [this message]
2023-10-31 11: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=MW2PR12MB466626AA060460A0ACEC8B2FD6A2A@MW2PR12MB4666.namprd12.prod.outlook.com \
--to=orika@nvidia.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=wenjing.qiao@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).