DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 948] flow create integrity  mlx5 ConnectX6 not supported inner l4_ok  l3_ok
Date: Thu, 03 Mar 2022 15:16:32 +0000	[thread overview]
Message-ID: <bug-948-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=948

            Bug ID: 948
           Summary: flow create integrity  mlx5 ConnectX6 not supported
                    inner l4_ok  l3_ok
           Product: DPDK
           Version: 21.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: killerstemp@gmail.com
  Target Milestone: ---

Red Hat Enterprise Linux Server release 7.9 (Maipo)


ofed_info -s
MLNX_OFED_LINUX-5.5-1.0.3.2:


mlxfwmanager   
Querying Mellanox devices firmware ...

Device #1:
----------

  Device Type:      ConnectX6
  Part Number:      MCX653106A-ECA_Ax
  Description:      ConnectX-6 VPI adapter card; H100Gb/s (HDR100; EDR IB and
100GbE); dual-port QSFP56; PCIe3.0 x16; tall bracket; ROHS R6
  PSID:             MT_0000000224
  PCI Device Name:  0000:98:00.0
  Base MAC:         b8cef6f974ee
  Versions:         Current        Available     
     FW             20.32.1010     N/A           
     PXE            3.6.0502       N/A           
     UEFI           14.25.0017     N/A           

  Status:           No matching image found


./dpdk-testpmd -l 5,7,9,11,13,15,17 -n 4 -- -i --rxq 6 --txq 6 --nb-cores 6
--rxd 2048 --txd 2048 --portmask 0xff --enable-rx-cksum

flow create 0 ingress pattern eth / ipv4 / tcp / integrity value mask 8 value
spec 8 / end actions count / queue index 0 / end
return error msg: integrity_item not supported: Operation not supported


gdb dpdk-testpmd find

dpdk-21.11\drivers\common\mlx5
->mlx5_devx_cmds.c->mlx5_devx_query_pkt_integrity_match()

        printf("inner_l3_ok =%d\n ",
                MLX5_GET(flow_table_nic_cap, hcattr,
                        ft_field_support_2_nic_receive.inner_l3_ok)
                );
        printf("inner_l4_ok =%d\n ",
                MLX5_GET(flow_table_nic_cap, hcattr,
                        ft_field_support_2_nic_receive.inner_l4_ok)
                );
        printf("outer_l3_ok =%d\n ",
                MLX5_GET(flow_table_nic_cap, hcattr,
                        ft_field_support_2_nic_receive.outer_l3_ok)
                );
        printf("outer_l4_ok =%d\n ",
                MLX5_GET(flow_table_nic_cap, hcattr,
                        ft_field_support_2_nic_receive.outer_l4_ok)
                );
        printf("inner_ipv4_checksum_ok =%d\n ",
                MLX5_GET(flow_table_nic_cap, hcattr,
                        ft_field_support_2_nic_receive.inner_ipv4_checksum_ok)
                );
        printf("outer_ipv4_checksum_ok =%d\n ",
                MLX5_GET(flow_table_nic_cap, hcattr,
                        ft_field_support_2_nic_receive.outer_ipv4_checksum_ok)
                );

inner_l3_ok =0
 inner_l4_ok =0
 outer_l3_ok =0
 outer_l4_ok =0
 inner_ipv4_checksum_ok =0
 outer_ipv4_checksum_ok =0

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2022-03-03 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 15:16 bugzilla [this message]
2022-08-28 20:56 ` bugzilla

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=bug-948-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /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).