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 8A04C4554D; Tue, 2 Jul 2024 16:21:21 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7AE49402B1; Tue, 2 Jul 2024 16:21:21 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id B9DBD402AD for ; Tue, 2 Jul 2024 16:21:19 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id A8CA04554F; Tue, 2 Jul 2024 16:21:19 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [DPDK/testpmd Bug 1479] mlx5: Not able to create rte_flows to match head fragments and sub fragments Date: Tue, 02 Jul 2024 14:21:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: testpmd X-Bugzilla-Version: 21.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: pingtosiva@gmail.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17199300790.2CC4De6c1.1684012 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 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 --17199300790.2CC4De6c1.1684012 Date: Tue, 2 Jul 2024 16:21:19 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1479 Bug ID: 1479 Summary: mlx5: Not able to create rte_flows to match head fragments and sub fragments Product: DPDK Version: 21.11 Hardware: All OS: All Status: UNCONFIRMED Severity: major Priority: Normal Component: testpmd Assignee: dev@dpdk.org Reporter: pingtosiva@gmail.com Target Milestone: --- I am trying to create an RTE flow rule to match head and non-head fragments= to compute NIC RSS based on 5tuple/3tuple respectively on connectX-6 DX NIC and mlx5 driver.=20 As part of it when trying to install RTE flow rule using testpmd on dpdk 21.11/23.07 version, the following errors are thrown. Flow rule to match head fragment =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D testpmd> flow create 0 ingress pattern eth / ipv4 fragment_offset spec 0x2= 000 fragment_offset mask 0x3fff / end actions drop / count / end port_flow_complain(): Caught PMD error type 13 (specific pattern item): cau= se: 0x7ffd1954c548, match on first fragment not supported: Operation not suppor= ted Flow rule to match non-head fragments =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D testpmd> flow validate 0 ingress pattern eth / ipv4 fragment_offset is 0x20= 01 fragment_offset last 0x1fff / end actions drop / end port_flow_complain(): Caught PMD error type 11 (item specification range): cause: 0x7ffc6f629534, specified range not supported: Operation not support= ed When I browsed mlx5_flow_dv.c driver file, there are set of conditions implemented to block this configurations. Could you kindly help is there a way to compute different RSS hash for fragments and non-fragments using RTE flow rules on mellanox? Thanks! in advance. /* * Match on fragment_offset 0x2000 means MF is 1 and frag-offset is= 0, * indicating this is 1st fragment of fragmented packet. * This is not yet supported in MLX5, return appropriate error mess= age. */ if (fragment_offset_spec =3D=3D RTE_BE16(RTE_IPV4_HDR_MF_FLAG)) return rte_flow_error_set(error, ENOTSUP, RTE_FLOW_ERROR_TYPE_ITEM, item, "match on first fragment not " "supported"); if (fragment_offset_spec && !last) return rte_flow_error_set(error, ENOTSUP, RTE_FLOW_ERROR_TYPE_ITEM, item, "specified value not supported"); /* * Match on fragment_offset spec 0x2001 and last 0x3fff * means MF is 1 and frag-offset is > 0. * This packet is fragment 2nd and onward, excluding last. * This is not yet supported in MLX5, return appropriate * error message. */ if (fragment_offset_spec =3D=3D RTE_BE16(RTE_IPV4_HDR_MF_FLAG + 1) = && fragment_offset_last =3D=3D RTE_BE16(MLX5_IPV4_FRAG_OFFSET_MASK= )) return rte_flow_error_set(error, ENOTSUP, RTE_FLOW_ERROR_TYPE_ITEM_LAST, last, "match on following " "fragments not supported"); /* * Match on fragment_offset spec 0x0001 and last 0x1fff * means MF is 0 and frag-offset is > 0. * This packet is last fragment of fragmented packet. * This is not yet supported in MLX5, return appropriate * error message. */ if (fragment_offset_spec =3D=3D RTE_BE16(1) && fragment_offset_last =3D=3D RTE_BE16(RTE_IPV4_HDR_OFFSET_MASK)) return rte_flow_error_set(error, ENOTSUP, RTE_FLOW_ERROR_TYPE_ITEM_LAST, last, "match on last " "fragment not supported"); --=20 You are receiving this mail because: You are the assignee for the bug.= --17199300790.2CC4De6c1.1684012 Date: Tue, 2 Jul 2024 16:21:19 +0200 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID 1479
Summary mlx5: Not able to create rte_flows to match head fragments an= d sub fragments
Product DPDK
Version 21.11
Hardware All
OS All
Status UNCONFIRMED
Severity major
Priority Normal
Component testpmd
Assignee dev@dpdk.org
Reporter pingtosiva@gmail.com
Target Milestone --- 

I am trying to create an RTE flow =
rule to match head and non-head fragments to
compute NIC RSS based on 5tuple/3tuple respectively on connectX-6 DX NIC and
mlx5 driver.=20

As part of it when trying to install RTE flow rule using testpmd on dpdk
21.11/23.07 version, the following errors are thrown.

Flow rule to match head fragment
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
testpmd>  flow create 0 ingress pattern eth / ipv4 fragment_offset spec =
0x2000
fragment_offset mask 0x3fff / end actions drop / count / end
port_flow_complain(): Caught PMD error type 13 (specific pattern item): cau=
se:
0x7ffd1954c548, match on first fragment not supported: Operation not suppor=
ted

Flow rule to match non-head fragments
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
testpmd> flow validate 0 ingress pattern eth / ipv4 fragment_offset is 0=
x2001
fragment_offset last 0x1fff / end actions drop / end
port_flow_complain(): Caught PMD error type 11 (item specification range):
cause: 0x7ffc6f629534, specified range not supported: Operation not support=
ed

When I browsed mlx5_flow_dv.c driver file, there are set of conditions
implemented to block this configurations.

Could you kindly help is there a way to compute different RSS hash for
fragments and non-fragments using RTE flow rules on mellanox?

Thanks! in advance.

       /*
         * Match on fragment_offset 0x2000 means MF is 1 and frag-offset is=
 0,
         * indicating this is 1st fragment of fragmented packet.
         * This is not yet supported in MLX5, return appropriate error mess=
age.
         */
        if (fragment_offset_spec =3D=3D RTE_BE16(RTE_IPV4_HDR_MF_FLAG))
                return rte_flow_error_set(error, ENOTSUP,
                                          RTE_FLOW_ERROR_TYPE_ITEM, item,
                                          "match on first fragment not=
 "
                                          "supported");
        if (fragment_offset_spec && !last)
                return rte_flow_error_set(error, ENOTSUP,
                                          RTE_FLOW_ERROR_TYPE_ITEM, item,
                                          "specified value not support=
ed");
        /*
         * Match on fragment_offset spec 0x2001 and last 0x3fff
         * means MF is 1 and frag-offset is > 0.
         * This packet is fragment 2nd and onward, excluding last.
         * This is not yet supported in MLX5, return appropriate
         * error message.
         */
        if (fragment_offset_spec =3D=3D RTE_BE16(RTE_IPV4_HDR_MF_FLAG + 1) =
&&
            fragment_offset_last =3D=3D RTE_BE16(MLX5_IPV4_FRAG_OFFSET_MASK=
))
                return rte_flow_error_set(error, ENOTSUP,
                                          RTE_FLOW_ERROR_TYPE_ITEM_LAST,
                                          last, "match on following &q=
uot;
                                          "fragments not supported&quo=
t;);
        /*
         * Match on fragment_offset spec 0x0001 and last 0x1fff
         * means MF is 0 and frag-offset is > 0.
         * This packet is last fragment of fragmented packet.
         * This is not yet supported in MLX5, return appropriate
         * error message.
         */
        if (fragment_offset_spec =3D=3D RTE_BE16(1) &&
            fragment_offset_last =3D=3D RTE_BE16(RTE_IPV4_HDR_OFFSET_MASK))
                return rte_flow_error_set(error, ENOTSUP,
                                          RTE_FLOW_ERROR_TYPE_ITEM_LAST,
                                          last, "match on last "
                                          "fragment not supported"=
;);

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --17199300790.2CC4De6c1.1684012--