From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Qiao, Wenjing" <wenjing.qiao@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v4] net/cpfl: support action prog
Date: Mon, 6 Nov 2023 01:50:43 +0000 [thread overview]
Message-ID: <DM4PR11MB5994336DC37F81B9BD0B70BCD7AAA@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231102085041.370159-1-wenjing.qiao@intel.com>
> -----Original Message-----
> From: Qiao, Wenjing <wenjing.qiao@intel.com>
> Sent: Thursday, November 2, 2023 4:51 PM
> To: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>;
> Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: dev@dpdk.org; Qiao, Wenjing <wenjing.qiao@intel.com>
> Subject: [PATCH v4] net/cpfl: support action prog
>
> From: Wenjing Qiao <wenjing.qiao@intel.com>
>
> Parse JSON file and generate rules that instruct PMD to map an
> RTE_FLOW_ACTION_TYPE_PROG to a low-level FXP representation, the
> matching follows below guidelines.
>
> Use rte_flow_action_prog->name to match the name of a P4 action type
> when provided in the JSON file. In cases where the JSON file lacks the P4
> action type's name but includes the P4 action type ID, PMD should attempt to
> convert rte_flow_action_prog->name into a
> uint32 value and then match it to the P4 action type ID.
>
> The same method applies when matching a rte_flow_action_prog_argument
> to a field of an action type.
>
> Here's an example to create a rule that matches an IPV4/TCP header and
> applies a VXLAN encapsulation which is represented by rte_flow_action_prog:
>
> flow create 0 ingress pattern eth src is 00:11:22:33:44:55 dst is
> 00:01:00:00:03:14 / ipv4 src is 192.168.0.1 dst is 192.168.0.2 / tcp src is 0x1451
> dst is 0x157c / end actions prog name vxlan_encap arguments src_addr
> 0xC0A80002 dst_addr 0xC0A80003 src_mac 0x000100000314 dst_mac
> 0x000600000314 src_port 0x1234 dst_port 0x4789 vni 0x000050 end /
> port_representor port_id 0 / end
>
> Signed-off-by: Wenjing Qiao <wenjing.qiao@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
The CI build error in patchwork is covered by below fix
https://patchwork.dpdk.org/project/dpdk/patch/20231106091453.1599496-1-qi.z.zhang@intel.com/
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2023-11-06 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 9:42 [PATCH] " wenjing.qiao
2023-10-30 2:13 ` [PATCH v2] " wenjing.qiao
2023-10-31 7:48 ` [PATCH v3] " wenjing.qiao
2023-10-31 8:12 ` Zhang, Qi Z
2023-11-02 8:50 ` [PATCH v4] " wenjing.qiao
2023-11-06 1:50 ` Zhang, Qi Z [this message]
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=DM4PR11MB5994336DC37F81B9BD0B70BCD7AAA@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@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).