From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7D25C42809; Wed, 22 Mar 2023 15:05:07 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6D3A1410EF; Wed, 22 Mar 2023 15:05:07 +0100 (CET) Received: from mx0b-00154904.pphosted.com (mx0b-00154904.pphosted.com [148.163.137.20]) by mails.dpdk.org (Postfix) with ESMTP id 024E240A7A for ; Tue, 21 Mar 2023 10:43:25 +0100 (CET) Received: from pps.filterd (m0170396.ppops.net [127.0.0.1]) by mx0b-00154904.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 32L51LwP020103; Tue, 21 Mar 2023 05:43:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dell.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=smtpout1; bh=yZThF2sfPL7lnBHAbnwP5MG6ODe8WwlNszSKTNgAe04=; b=vqlJUcZsb3Ur/F3Q68kLmoSUuOqpbXF6Tt4JHSary0/kLl0oqwg4l4EqVdEwquxmVVGt QFFSn+jDFWWr9lnmn6Gpu1H8KLoUX1vgRlWTGpG8Gj16gpautKis8VNEYLtKZnxPhOFu R0ALwFWMNZloUOcT5Z8U76gEVT3KTMcN3ApwtmOmI3iUTe+nN8oahcm3Jnc+RhLEMCPY jFdwmjOwA62vf4qp85SXfqD77Fo0v/iu6a9OiVnfPn2yki/3bV8gXf09uFxKV7Lu6Te/ GNFE0fsZfcBpW+hwbeZ1GvFuWX1O4wQa7JwD15qRESOf04CN/Q2V7RvOlFE0obisWHuR zg== Received: from mx0b-00154901.pphosted.com (mx0b-00154901.pphosted.com [67.231.157.37]) by mx0b-00154904.pphosted.com (PPS) with ESMTPS id 3pd950as4p-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 21 Mar 2023 05:43:24 -0400 Received: from pps.filterd (m0144103.ppops.net [127.0.0.1]) by mx0b-00154901.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 32L7wv7V026141; Tue, 21 Mar 2023 05:43:24 -0400 Received: from nam10-mw2-obe.outbound.protection.outlook.com (mail-mw2nam10lp2107.outbound.protection.outlook.com [104.47.55.107]) by mx0b-00154901.pphosted.com (PPS) with ESMTPS id 3pf8nr9dys-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 21 Mar 2023 05:43:24 -0400 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=d0+CTra+4NdGuaBrUDXuhynO8SjW1xlgU7zR6leJMvrztKNDrIxdspFB32Obm0gRiT2aSVRttn4nM5vmiwq3sxfhcNM1/mNLKprQUSylv4i4AWP//pOiY0myie/uFFgd3dChxxOIq/YQEEA+OFMfKHdoqvlLsbIUOWgPyNP8x2SVe8R9Vkg1q5MFO2eTFz3ZEqz5fww7wfh7/L6AoM9WMCQJ2HID2/ivuVWKG6WJk+PVNUPU6XnniLnYMlyyWdNZMmoYxiVeNe84E6tY5Ot5UROl0AIULHTHI3L8gJ8Ugr0RrQsOY3VH+3qbPD/Q8mIE4/g3lNrX+3Cl0VTdwskY8A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=yZThF2sfPL7lnBHAbnwP5MG6ODe8WwlNszSKTNgAe04=; b=VQfD6cUHZ7ZY5HpYlQBMUeJg/rNYRZB/WMApO4Bp/xEzEeh9iOqP/4b7W+l46sVbbHptnqXTZzoi+FYcAVMOkNqxcdG+11H1ZwzZdRLVrvmzTAemoNpmduFrfjXCmZ/j/a5sNdEVF/99DJdvBZxu8KEB+W+MZ1NadxxIW8UjTnH2SjGbT6jR1toWfuXLWpzkfYhR0hLFi0/L7vH8/Yhgt86ETsIzbpPJ29Mm0QQ7rqzChnkPF/DPNqheKragc2l7JwvJoJnXjTmi+q23S3u3VJl51VTRkR2jesbypg/Z0yANURK9ZF6OBSjixa4ED1viZLXTpZYbxYEmaEHbn8MTtQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=dell.com; dmarc=pass action=none header.from=dell.com; dkim=pass header.d=dell.com; arc=none Received: from MW5PR19MB5554.namprd19.prod.outlook.com (2603:10b6:303:193::6) by PH7PR19MB5485.namprd19.prod.outlook.com (2603:10b6:510:139::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6086.23; Tue, 21 Mar 2023 09:42:52 +0000 Received: from MW5PR19MB5554.namprd19.prod.outlook.com ([fe80::6381:1eb1:5a5b:ec71]) by MW5PR19MB5554.namprd19.prod.outlook.com ([fe80::6381:1eb1:5a5b:ec71%9]) with mapi id 15.20.6086.023; Tue, 21 Mar 2023 09:42:52 +0000 From: "Krishna, Parameswaran" To: Raslan Darawsheh , "dev@dpdk.org" CC: Ori Kam Subject: RE: MLX5 : Having RTE_FLOW_ACTION_TYPE_PORT_ID flow entry and RTE_FLOW_ACTION_TYPE_QUEUE flow entry in same flow group Thread-Topic: MLX5 : Having RTE_FLOW_ACTION_TYPE_PORT_ID flow entry and RTE_FLOW_ACTION_TYPE_QUEUE flow entry in same flow group Thread-Index: AdlbHxpozQySdAykSNmLmoT5pnXxogAJTmegACUei3A= Date: Tue, 21 Mar 2023 09:42:52 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_73dd1fcc-24d7-4f55-9dc2-c1518f171327_Enabled=true; MSIP_Label_73dd1fcc-24d7-4f55-9dc2-c1518f171327_SetDate=2023-03-21T09:42:50Z; MSIP_Label_73dd1fcc-24d7-4f55-9dc2-c1518f171327_Method=Standard; MSIP_Label_73dd1fcc-24d7-4f55-9dc2-c1518f171327_Name=No Protection (Label Only) - Internal Use; MSIP_Label_73dd1fcc-24d7-4f55-9dc2-c1518f171327_SiteId=945c199a-83a2-4e80-9f8c-5a91be5752dd; MSIP_Label_73dd1fcc-24d7-4f55-9dc2-c1518f171327_ActionId=0110e61a-9f5e-4b7d-bc37-1737ce1a9f7b; MSIP_Label_73dd1fcc-24d7-4f55-9dc2-c1518f171327_ContentBits=2 x-ms-publictraffictype: Email x-ms-traffictypediagnostic: MW5PR19MB5554:EE_|PH7PR19MB5485:EE_ x-ms-office365-filtering-correlation-id: 6e6970fa-d127-47fb-ed3f-08db29f0a3e7 x-exotenant: 2khUwGVqB6N9v58KS13ncyUmMJd8q4 x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: pxsxCKDd94qGwBznn+ded9RM3ns5R06UvWqGe8PisqLeFeIVBTqgrvZfkjFGtrWetsL9CbOcNXwTqT6bUKWpar01dymMrVWBeQfEt+t6/QE/m0Ip9bo0I9cZA1FeMgmUkSCXNXDxJcbcbNoBu0aho0CCgCLrFLcYOR+R3CYoFNGlIAOCB3UpvJUotAJYbIQzf7W7xFFhJmW+W4m2NzO7l9zXFZs7DUFsmMsTRHSOwfd/jKnHGJ2LasinVhKCOH07Umyfz0DL7gZT+lVLGeWFlh/RDiaXVyEKRsck7eIF4J0P/9lrPGIvmMHg5oPQDCCK3pKCjDlEBF+jcd5Peq2jQc5AXHpP+RYI+/eNbiMfq9z+CwtnFSC/4gpU6zMCYVVz0YBBpNd5rjcstL0XikPYGJneVSVaKKMSxUvTGm7IJomS5P7tFyVuKC+gboegVLUtqknkvdCdl3O6bPkGJ5zDJBLiAC2YBh0boAftt5npekH7MymRCgiqR94htcI7E9Y/qJ41nxdvrWghwop1se56gok61QAjQ25i9ar5dk9TU+vdWwcKWaNslay7wRDmxsPK+B5MyUHdovycrLuoJTZw1yDEiFZ8wH1E8YTa0sltnRq50Ax+NAxQYB9YpFZ6nqDJo0XOH89XWTlYWbYGxGhy9O9aT+Brep8O/e3ZAcsrkXcvb95us+VRkt5U7pkdAsStavHylh7Uyx/Ol/EyI9Oh0A== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MW5PR19MB5554.namprd19.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230025)(4636009)(346002)(396003)(39860400002)(366004)(376002)(136003)(451199018)(86362001)(66556008)(478600001)(9686003)(53546011)(66476007)(71200400001)(76116006)(4326008)(66946007)(64756008)(8676002)(26005)(186003)(7696005)(66446008)(41300700001)(110136005)(6506007)(83380400001)(786003)(52536014)(82960400001)(38070700005)(55016003)(33656002)(122000001)(316002)(8936002)(2906002)(38100700002)(5660300002); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?i54agWKb6Oi3n7J3vSqM02J+6QAXDamocSUjKfloYHfw532nAQKF7bpdwgTI?= =?us-ascii?Q?Sw1+N0wVDTfcERzyjUaAgC6QSdSVLjwwN7z4hRkENaCyh1UEjrPL4sxTAyMl?= =?us-ascii?Q?Xv1HW7w3/vGHONaWBkKI1Sf68Ncg2mTzQ9ZdnCBSpG+zI/99qwKZsHIOfjkK?= =?us-ascii?Q?nLFH7fNRgYJLhGjXK6qPwbHBtdZ31MJ7WSZfNWEVROV32uT/cbJnLofXDcU3?= =?us-ascii?Q?U+hkdZ3MNT/54W24+DmYpGM6wA1YnPoFmBxffdUG+jTfWvCFW7nJH6vyCrtJ?= =?us-ascii?Q?fi+ICollmNeQVOeFWjusKlu4WPwIk3jrXMiiq0kAQ1Knd0gU2k70pcl6kGfb?= =?us-ascii?Q?ai//G5RDYhqxgoRpG3N0cCSEAOqLDXiSlWu3awz761B94MbavaMI9ACsxIWe?= =?us-ascii?Q?HRMHdQk5WQsMdID3fM12D4X/mMozkH3pBTKkkInGRQHENlSG5pPsBcP1Ldeb?= =?us-ascii?Q?eIZK0o7Q6EO+v5ZyVbF+gD2gPyfnK8qNuu7XrDR0L2EjRBnK35ucEzd5IDCR?= =?us-ascii?Q?chBBHz3vpUkExFZntvvI1AlJHciBjRRK0YNEmaTIj41h0TzIr9cSGtAF0Uss?= =?us-ascii?Q?oTyf/u3bbBPGldZfpjKaU45tKc7iig9c2WJ30Ly5YjqAPznwkwK9GShEQil+?= =?us-ascii?Q?yvDjFtzWtZdvQVkC/3eph+7ZrMEAhOf//TSm/iuQjlwWLMIdqaOcUuCY7997?= =?us-ascii?Q?zuP7kws6IK088Jb63wdPAxpjO8JkebTKNlofSejA+j7Z1MMNEKPITIJvlwed?= =?us-ascii?Q?zuXndUBbcWhEQVMIFp/r4PFTtEoizy38VE++A9pYIu9VDpnriSZY9GTlMNy+?= =?us-ascii?Q?fMYrKARqtNkuC1ai0Pl1AwODIV+i6RLraFdyrzW1ZmS8Cy5B42qwK2lBf+X4?= =?us-ascii?Q?5ZFrDHECfWtY6qxSmXqUrNfkN0wgOi7otib6V9zMDdFj3vFa8lPpo3sbJ7pD?= =?us-ascii?Q?JBojofQy1Ihvxv5uXzcSJO8deyFNEOOjbuKJcS2M5wpsA6NE1xwwF1XMBs/y?= =?us-ascii?Q?tGD2IHu7b/AdhkpOLrP3w3e28NKfq/vo7N9hZ2Wuqls45caSmgQrHNZ7jgaY?= =?us-ascii?Q?H5ZkidWIvUAMc8ctw4THV7CheWywpgnB8/7nJp+F9MvtQ6cWfVPduVSze/zc?= =?us-ascii?Q?MpnsKEkcVVYqGRjKmBC6Y/EeNhDGOkzjzqLeIljr9SE5Z0SM+KQgMsi8VP5F?= =?us-ascii?Q?teTC4thiYnJ5HgWDz4hd194M5KroYkQT1FhiLeIGaUTiELdDX1OtiVoMl6it?= =?us-ascii?Q?qBWY0FyYAQnmBaCT9eemgzdPm4btfO/Z3sl6NHzUeTpfJLSj/d7bZtAZwTls?= =?us-ascii?Q?keLZzg5g61/KNTvfhEP/VTwb8I0BfAOImFiB1NALnG05dJZnP+W987x0/jqa?= =?us-ascii?Q?oDK51T9+97H4KWXaWHYbg0np380hOkssfw7LNTNFb5D9kjjYbZHQCVU9raj7?= =?us-ascii?Q?cVRdbLhqdh0wltVJxrGLsGzpAN0YEMz27CFIre3s9zjSu/tXp6FZdjaaPSwM?= =?us-ascii?Q?RFZ+n9+9zYcafacMd/xpJ1BVzyhZXdD8asQnSdXbXe4Jy2h5hw+Uf9FUP5Kc?= =?us-ascii?Q?1uL2bxVaJ2Mifysf9owhxhzN7sk7rR/yYSMjP9YL7Y8KFc6Zix4spii/iwbr?= =?us-ascii?Q?8A=3D=3D?= Content-Type: multipart/alternative; boundary="_000_MW5PR19MB5554DD9DE8CE4608D1B37E8B9D819MW5PR19MB5554namp_" MIME-Version: 1.0 X-OriginatorOrg: Dell.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: MW5PR19MB5554.namprd19.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 6e6970fa-d127-47fb-ed3f-08db29f0a3e7 X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Mar 2023 09:42:52.1676 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 945c199a-83a2-4e80-9f8c-5a91be5752dd X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: U+9RoyO4ljaW0Q9MBqYf+/hR1/pFFVXlW3tBbbiQz6fZHsyvlFAAflc5PSCYcsC7pEwYij0saevWFft8kIqAjezGaqDd3Sz1sP/XHRDtELo= X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH7PR19MB5485 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.942,Hydra:6.0.573,FMLib:17.11.170.22 definitions=2023-03-21_07,2023-03-20_02,2023-02-09_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 mlxscore=0 lowpriorityscore=0 adultscore=0 spamscore=0 impostorscore=0 bulkscore=0 clxscore=1011 malwarescore=0 suspectscore=0 mlxlogscore=999 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2303150002 definitions=main-2303210075 X-Proofpoint-ORIG-GUID: in1zvbTypUhGYCyNlc2YthhZaEk5GDnp X-Proofpoint-GUID: in1zvbTypUhGYCyNlc2YthhZaEk5GDnp X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 malwarescore=0 suspectscore=0 clxscore=1011 mlxscore=0 priorityscore=1501 mlxlogscore=999 adultscore=0 phishscore=0 lowpriorityscore=0 bulkscore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2303150002 definitions=main-2303210073 X-Mailman-Approved-At: Wed, 22 Mar 2023 15:05:06 +0100 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --_000_MW5PR19MB5554DD9DE8CE4608D1B37E8B9D819MW5PR19MB5554namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Raslan Darawsheh, Thanks for the details. It is very useful. Now I understand that the behavi= or observed is expected. Best regards, Parameswaran Krishnamurthy Internal Use - Confidential From: Raslan Darawsheh Sent: Monday, March 20, 2023 9:32 PM To: Krishna, Parameswaran; dev@dpdk.org Cc: Ori Kam Subject: RE: MLX5 : Having RTE_FLOW_ACTION_TYPE_PORT_ID flow entry and RTE_= FLOW_ACTION_TYPE_QUEUE flow entry in same flow group [EXTERNAL EMAIL] Hi Krishna, You have two types of tables: 1. FDB (those are the ones with the transfer attribute being set to 1) 2. NIC ( those are the ones with the ingress attribute only being set to= 1) When you do jump from one group to another on FDB it will not reach the NIC= groups 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 group). The second flow is on the NIC table which needs another root table flow to = jump to it from group 0 on NIC. So the order of execution for the tables would be like follows: 1. FDB: group 0 -> .... Group N 2. NIC: group 0 -> group N. If a packet will miss on an FDB table it will be redirected to NIC table on= group 0. If a packet will miss on a NIC table group > 0 it will be dropped. Kindest regards, Raslan Darawsheh From: Krishna, Parameswaran > Sent: Monday, March 20, 2023 1:31 PM To: dev@dpdk.org Cc: Ori Kam > Subject: MLX5 : Having RTE_FLOW_ACTION_TYPE_PORT_ID flow entry and RTE_FLOW= _ACTION_TYPE_QUEUE flow entry in same flow group Hi Experts, 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. I installed a flow rule in group 0 with Attribute Transfer=3D1, matching sr= c-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. Then In Group1, I installed a flow rule with Attribute Transfer=3D0, matchi= ng 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=3D0 is mand= atory. Setting Transfer to 1 reported error "unsupported action QUEUE". Thi= s rule seem to have got installed in NIC_RX table. 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. When I installed the JUMP action rule in group 0 with Transfer=3D0, the RTE= _FLOW_ACTION_TYPE_QUEUE rule entry in group 1 got hit successfully. With Tr= ansfer=3D0 set for both the rules, I guess both the rules got installed in = NIC_RX table and the JUMP action worked fine. But the problem is, now I'm unable to get a rule with action RTE_FLOW_ACTIO= N_TYPE_PORT_ID in group1 get hit as RTE_FLOW_ACTION_TYPE_PORT_ID insists on= setting Transfer=3D1 and this rule is getting installed in FDB table. Is there any means by which I can have both RTE_FLOW_ACTION_TYPE_PORT_ID fl= ow entry and RTE_FLOW_ACTION_TYPE_QUEUE flow entry in Group 1 and get them = hit when jumped from Group 0 ? Any input is highly appreciated. Thanks in advance. root@server:/mlx_steering_dump/sws# python3 mlx_steering_dump_parser.py -p = 87 -f /tmp/DpdkDump -t -port 0 domain 0x5702: type: FDB, gvmi: 0x4, support_sw_steering True, dev_name uve= rbs0, package_version 38.0, flags None, ste_buddies None, mh_buddies None, = ptrn_buddies None table 0xaaaad5ba9520: level: 1, type: FDB matcher 0xaaaad5ada050: priority 2, rx e_anchor 0xf0200015, tx e_an= chor 0xf0200017 mask: smac: 0xffffffffffff, cvlan_tag: 0x1, metadata_reg_c_0: 0x= ffff0000 rule 0xaaaad5699610 match: metadata_reg_c_0: 0x00030000, smac: ce:25:02:c2:a0:f2 action: FT devx id 0x15, dest_ft 0xaaaad5682c30 & CTR(counter= ), index 0x8011fd table 0xaaaad5ba9110: level: 0, type: ROOT table 0xaaaad5682c30: level: 11, type: FDB 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 Non= e, ptrn_buddies None table 0xaaaad550c550: level: 0, type: ROOT table 0xaaaad56829a0: level: 10, type: NIC_RX matcher 0xaaaad5af1010: priority 2, rx e_anchor 0xf010003a mask: smac: 0xffffffffffff, cvlan_tag: 0x1, metadata_reg_c_0: 0x= ffff0000 rule 0xaaaad5682bb0 match: metadata_reg_c_0: 0x00030000, smac: ce:25:02:c2:a0:f2 action: CTR(counter), index 0x8011fe & DEVX_TIR, ICM addr 0x4= 6f2800014b40 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 Non= e, ptrn_buddies None Best Regards, Parameswaran Krishnamurthy Internal Use - Confidential --_000_MW5PR19MB5554DD9DE8CE4608D1B37E8B9D819MW5PR19MB5554namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Raslan Darawsheh,

 

Thanks for the details. It is very useful. Now I und= erstand that the behavior observed is expected.

 

Best regards,

Parameswaran Krishnamurthy

 

 

Internal Use - Confidential

From: Raslan Darawsheh <rasland@nvidia.com= >
Sent: Monday, March 20, 2023 9:32 PM
To: Krishna, Parameswaran; dev@dpdk.org
Cc: Ori Kam
Subject: RE: MLX5 : Having RTE_FLOW_ACTION_TYPE_PORT_ID flow entry a= nd RTE_FLOW_ACTION_TYPE_QUEUE flow entry in same flow group

 

[EXTERNAL EMAIL]

Hi &= nbsp; Krishna,

&nbs= p;

You have = two types of tables:

  1. FDB (those are the ones wi= th the transfer attribute being set to 1)
  2. NIC ( those are the ones with the i= ngress attribute only being set to 1)

&nbs= p;

When you = do jump from one group to another on FDB it will not reach the NIC groups

It will j= ump to an FDB table (group 1) and in your case,  it’s empty (sin= ce you don’t have any flow in that

group).

&nbs= p;

The secon= d flow is on the NIC table which needs another root table flow to jump to i= t from group 0 on NIC.

&nbs= p;

So the or= der of execution for the tables would be like follows:

  1. FDB: group 0 -> …= . Group N
  2. NIC: group 0 -> group N.

&nbs= p;

If a pack= et will miss on an FDB table it will be redirected to NIC table on group 0.=

If a pack= et will miss on a NIC table group > 0 it will be dropped.

&nbs= p;

Kindest regards,

Raslan Darawsheh

&nbs= p;

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 R= TE_FLOW_ACTION_TYPE_QUEUE flow entry in same flow group

 

Hi Experts,

 

I’m using DPDK 21.08 with Mlx5 NIC. I’m = trying to configure rte-flows with multiple groups. I’m observing tha= t under certain circumstances, jump-group action from Group-0 to Group-1 is= not working.

 

I installed a flow rule in group 0 with Attribute Tr= ansfer=3D1, matching src-mac ce:25:02:c2:a0:f2 and action to VNET_FLOW_ACTI= ON_JUMP_GROUP to Group 1.This rule seem to have got installed in FDB table.=

 

Then In Group1, I installed a flow rule with Attribu= te Transfer=3D0, matching src-mac ce:25:02:c2:a0:f2 and action RTE_FLOW_ACT= ION_TYPE_QUEUE to queue 0. For RTE_FLOW_ACTION_TYPE_QUEUE, looks like setti= ng Transfer=3D0 is mandatory. Setting Transfer to 1 reported error “unsupported action QUEUE”. This = rule seem to have got installed in NIC_RX table.

 

Now, When I set packets from ce:25:02:c2:a0:f2, it h= it the rule in Group 0, but did not hit the rule in Group 1. Looks like JUM= P from FDB table to NIC_RX table is not happening.

 

When I installed the JUMP action rule in group 0 wit= h Transfer=3D0, the RTE_FLOW_ACTION_TYPE_QUEUE rule entry in group 1 got hi= t successfully. With Transfer=3D0 set for both the rules, I guess both the = rules got installed in NIC_RX table and the JUMP action worked fine.

 

But the problem is, now I’m unable to get a ru= le with action RTE_FLOW_ACTION_TYPE_PORT_ID in group1 get hit as RTE_FLOW_A= CTION_TYPE_PORT_ID insists on setting Transfer=3D1 and this rule is getting= installed in FDB table.

 

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 i= n Group 1 and get them hit when jumped from Group 0 ?

 

Any input is highly appreciated. Thanks in advance.<= o:p>

 

root@server:/mlx_steering_dump/sws# python3 mlx_stee= ring_dump_parser.py -p 87 -f /tmp/DpdkDump -t -port 0

domain 0x5702: type: FDB, gvmi: 0x4, support_sw_stee= ring True, dev_name uverbs0, package_version 38.0, flags None, ste_buddies = None, mh_buddies None, ptrn_buddies None

     table 0xaaaad5ba9520: le= vel: 1, type: FDB

        matcher 0= xaaaad5ada050: priority 2, rx e_anchor 0xf0200015, tx e_anchor 0xf0200017

        &nbs= p;  mask: smac: 0xffffffffffff, cvlan_tag: 0x1, metadata_reg_c_0: 0xff= ff0000

        &nbs= p;  rule 0xaaaad5699610

        &nbs= p;     match: metadata_reg_c_0: 0x00030000, smac: ce:25= :02:c2:a0:f2

        &nbs= p;     action: FT devx id 0x15, dest_ft 0xaaaad5682c= 30 & CTR(counter), index 0x8011fd

     table 0xaaaad5ba9110: level= : 0, type: ROOT

     table 0xaaaad5682c30: level= : 11, type: FDB

domain 0x5700: type: NIC_RX, gvmi: 0x4, support_sw_s= teering True, dev_name uverbs0, package_version 38.0, flags None, ste_buddi= es None, mh_buddies None, ptrn_buddies None

     table 0xaaaad550c550: level= : 0, type: ROOT

     t= able 0xaaaad56829a0: level: 10, type: NIC_RX

        matcher 0= xaaaad5af1010: priority 2, rx e_anchor 0xf010003a

        &nbs= p;  mask: smac: 0xffffffffffff, cvlan_tag: 0x1, metadata_reg_c_0: 0xff= ff0000

        &nbs= p;  rule 0xaaaad5682bb0

        &nbs= p;     match: metadata_reg_c_0: 0x00030000, smac: ce:25= :02:c2:a0:f2

        &nbs= p;     action: CTR(counter), index 0x8011fe & DEVX_= TIR, ICM addr 0x46f2800014b40

domain 0x5701: type: NIC_TX, gvmi: 0x4, support_sw_s= teering True, dev_name uverbs0, package_version 38.0, flags None, ste_buddi= es None, mh_buddies None, ptrn_buddies None

 

Best Regards,

Parameswaran Krishnamurthy

 

Internal Use - Confidential

--_000_MW5PR19MB5554DD9DE8CE4608D1B37E8B9D819MW5PR19MB5554namp_--