<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body link="#0563C1" vlink="#954F72" style="word-wrap:break-word"> <div class="WordSection1"> Hi Krishna,<o:p></o:p> <o:p> </o:p> You have two types of tables:<o:p></o:p> <ol style="margin-top:0in" start="1" type="1"> <li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">FDB (those are the ones with the transfer attribute being set to 1)<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">NIC ( those are the ones with the ingress attribute only being set to 1)<o:p></o:p></li></ol> <o:p> </o:p> When you do jump from one group to another on FDB it will not reach the NIC groups <o:p></o:p> It will jump to an FDB table (group 1) and in your case, it’s empty (since you don’t have any flow in that <o:p></o:p> group).<o:p></o:p> <o:p> </o:p> The second flow is on the NIC table which needs another root table flow to jump to it from group 0 on NIC.<o:p></o:p> <o:p> </o:p> So the order of execution for the tables would be like follows:<o:p></o:p> <ol style="margin-top:0in" start="1" type="1"> <li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo2">FDB: group 0 -> …. Group N<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo2">NIC: group 0 -> group N.<o:p></o:p></li></ol> <o:p> </o:p> If a packet will miss on an FDB table it will be redirected to NIC table on group 0.<o:p></o:p> If a packet will miss on a NIC table group > 0 it will be dropped.<o:p></o:p> <o:p> </o:p> <div> Kindest regards,<o:p></o:p> Raslan Darawsheh<o:p></o:p> </div> <o:p> </o:p> <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: Krishna, Parameswaran <Parameswaran.Krishna@dell.com> Sent: Monday, March 20, 2023 1:31 PM To: dev@dpdk.org Cc: Ori Kam <orika@nvidia.com> Subject: MLX5 : Having RTE_FLOW_ACTION_TYPE_PORT_ID flow entry and RTE_FLOW_ACTION_TYPE_QUEUE flow entry in same flow group<o:p></o:p> </div> </div> <o:p> </o:p> Hi Experts,<o:p></o:p> <o:p> </o:p> I’m using DPDK 21.08 with Mlx5 NIC. I’m trying to configure rte-flows with multiple groups. I’m observing that under certain circumstances, jump-group action from Group-0 to Group-1 is not working.<o:p></o:p> <o:p> </o:p> I installed a flow rule in group 0 with Attribute Transfer=1, matching src-mac ce:25:02:c2:a0:f2 and action to VNET_FLOW_ACTION_JUMP_GROUP to Group 1.This rule seem to have got installed in FDB table.<o:p></o:p> <o:p> </o:p> Then In Group1, I installed a flow rule with Attribute Transfer=0, matching src-mac ce:25:02:c2:a0:f2 and action RTE_FLOW_ACTION_TYPE_QUEUE to queue 0. For RTE_FLOW_ACTION_TYPE_QUEUE, looks like setting Transfer=0 is mandatory. Setting Transfer to 1 reported error “unsupported action QUEUE”. This rule seem to have got installed in NIC_RX table.<o:p></o:p> <o:p> </o:p> Now, When I set packets from ce:25:02:c2:a0:f2, it hit the rule in Group 0, but did not hit the rule in Group 1. Looks like JUMP from FDB table to NIC_RX table is not happening.<o:p></o:p> <o:p> </o:p> When I installed the JUMP action rule in group 0 with Transfer=0, the RTE_FLOW_ACTION_TYPE_QUEUE rule entry in group 1 got hit successfully. With Transfer=0 set for both the rules, I guess both the rules got installed in NIC_RX table and the JUMP action worked fine.<o:p></o:p> <o:p> </o:p> But the problem is, now I’m unable to get a rule with action RTE_FLOW_ACTION_TYPE_PORT_ID in group1 get hit as RTE_FLOW_ACTION_TYPE_PORT_ID insists on setting Transfer=1 and this rule is getting installed in FDB table.<o:p></o:p> <o:p> </o:p> Is there any means by which I can have both RTE_FLOW_ACTION_TYPE_PORT_ID flow entry and RTE_FLOW_ACTION_TYPE_QUEUE flow entry in Group 1 and get them hit when jumped from Group 0 ?<o:p></o:p> <o:p> </o:p> Any input is highly appreciated. Thanks in advance.<o:p></o:p> <o:p> </o:p> root@server:/mlx_steering_dump/sws# python3 mlx_steering_dump_parser.py -p 87 -f /tmp/DpdkDump -t -port 0<o:p></o:p> domain 0x5702: type: FDB, gvmi: 0x4, support_sw_steering True, dev_name uverbs0, package_version 38.0, flags None, ste_buddies None, mh_buddies None, ptrn_buddies None<o:p></o:p> table 0xaaaad5ba9520: level: 1, type: FDB<o:p></o:p> matcher 0xaaaad5ada050: priority 2, rx e_anchor 0xf0200015, tx e_anchor 0xf0200017<o:p></o:p> mask: smac: 0xffffffffffff, cvlan_tag: 0x1, metadata_reg_c_0: 0xffff0000<o:p></o:p> rule 0xaaaad5699610<o:p></o:p> match: metadata_reg_c_0: 0x00030000, smac: ce:25:02:c2:a0:f2<o:p></o:p> action: FT devx id 0x15, dest_ft 0xaaaad5682c30 & CTR(counter), index 0x8011fd<o:p></o:p> table 0xaaaad5ba9110: level: 0, type: ROOT<o:p></o:p> table 0xaaaad5682c30: level: 11, type: FDB<o:p></o:p> domain 0x5700: type: NIC_RX, gvmi: 0x4, support_sw_steering True, dev_name uverbs0, package_version 38.0, flags None, ste_buddies None, mh_buddies None, ptrn_buddies None<o:p></o:p> table 0xaaaad550c550: level: 0, type: ROOT<o:p></o:p> table 0xaaaad56829a0: level: 10, type: NIC_RX<o:p></o:p> matcher 0xaaaad5af1010: priority 2, rx e_anchor 0xf010003a<o:p></o:p> mask: smac: 0xffffffffffff, cvlan_tag: 0x1, metadata_reg_c_0: 0xffff0000<o:p></o:p> rule 0xaaaad5682bb0<o:p></o:p> match: metadata_reg_c_0: 0x00030000, smac: ce:25:02:c2:a0:f2<o:p></o:p> action: CTR(counter), index 0x8011fe & DEVX_TIR, ICM addr 0x46f2800014b40<o:p></o:p> domain 0x5701: type: NIC_TX, gvmi: 0x4, support_sw_steering True, dev_name uverbs0, package_version 38.0, flags None, ste_buddies None, mh_buddies None, ptrn_buddies None<o:p></o:p> <o:p> </o:p> Best Regards,<o:p></o:p> Parameswaran Krishnamurthy<o:p></o:p> <o:p> </o:p> Internal Use - Confidential<o:p></o:p> </div> </div> </body> </html>