From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5321BA04F6; Wed, 11 Dec 2019 16:58:01 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EB9602C6A; Wed, 11 Dec 2019 16:58:00 +0100 (CET) Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) by dpdk.org (Postfix) with ESMTP id 75AD11D9E for ; Wed, 11 Dec 2019 16:57:59 +0100 (CET) Received: by mail-lj1-f180.google.com with SMTP id s22so24642260ljs.7 for ; Wed, 11 Dec 2019 07:57:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind.com; s=google; h=mime-version:from:date:message-id:subject:to:cc; bh=hlQtHKObDzGyehwhSXC6VOHqbzBoTjXyApS2h3iBa5Y=; b=UDCf+5EnoQ906M4mGiKvGCa2FCrZXzjHmgE8+MgbxC3vi2G8rM5ERJdo/tfbCiPdMV /Foo3WDb7DTaWgA5UpdpeA+sa16Jn6JIE/CNGD116+P6PAKWXz/In56wKbbZWM0KdtlY piuBS3UGUhTWdux4Kf3A17Q3IGlUzd9/9aivxLvubbQub5bV5qsnBNnxbyzx5ds/qQKN ChEOfd1jnEG8iza/x9jj57B5RPrg1H/vMkrCkPL9OJA4ip/Bm+YbgXvt7Bo+Nng+d1Eu KamV4+6oH+a/6xUhuGc3GFVuDsvKTK3qwYmQolegS7zIhAoPpK6K0BxNBuvLnH7yhfoD WOSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=hlQtHKObDzGyehwhSXC6VOHqbzBoTjXyApS2h3iBa5Y=; b=Swby+nkin0WNWlF2KssU64rT9nedVYgEzh9oP2o8dhFLTDauK7bR7JFStdqJONGBGR 3JkGZVFsMvLb0ngfXBYCZAtIirz1I4kyglFuUVt8IY5S0GiGUHM8MVVWckmKj5jvnNru kyQDhuU9XsBhgdlgOFIISYuu02l8cpY3DAMGYMGmRzgUTe6e7eJm+A1VLk9LOyK5xrsp j7bnCw+A/bDwtA1a1fAZN4XXUrNeKHgy3gXlj0xrOrIYxKDxZ/+ugcb73fqsfkHEOK7U FfVkNplBSFqThofN70AGAEF5b9B4k1C3A7QESkQaRPu/HiAxkuRYc1MwFsfGv84ydhc+ BC7Q== X-Gm-Message-State: APjAAAVr6T5O8kTWZnJtzTg/HF1cBSj2+zmAyEwFBqR6Od1pcAYvfwqH ZlYEfpniGsYfv+zrMTeqNO/uZC3aXj1swqJfekxKg3a/ X-Google-Smtp-Source: APXvYqwpUzeCYbsaGL+ZKipOVGuIFWCbbJ7ngUfYhBL70hW0edBgrNFBQraKyMq+PnAKc64uzbWuE7PQoN57DUPYEpw= X-Received: by 2002:a2e:818e:: with SMTP id e14mr2531587ljg.2.1576079878804; Wed, 11 Dec 2019 07:57:58 -0800 (PST) MIME-Version: 1.0 From: Christophe Grosse Date: Wed, 11 Dec 2019 16:57:48 +0100 Message-ID: To: dev@dpdk.org Cc: ajit.khaparde@broadcom.com Content-Type: text/plain; charset="UTF-8" Subject: [dpdk-dev] BCM57414 VF Mode: max_rx_em_flows value is inconsistent X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hello, I am using DPDK 18.11.5 from dpdk-stable repository with a Broadcom network adapter in VF mode : Broadcom Limited BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller (rev 01) # ./bnxtnvm listdev Broadcom P225p NetXtreme-E Dual-port 10Gb/25Gb Ethernet PCIe Adapter #1 Device Interface Name : ntfp2 MACAddress : 00-0A-F7-B6-E3-D1 PCI Device Name : 0000:02:00.1 # ./bnxtnvm -dev=ntfp2 devid PCI VendorID : 14e4 PCI DeviceID : 16d7 PCI Subsys VendorID : 14e4 PCI Subsys DeviceID : 1402 PCI Device Name : 0000:02:00:1 # ./bnxtnvm -dev=ntfp2 pkgver Active Package version : 20.06.01.06 Package version on NVM : 20.06.01.06 I added a log inside function __bnxt_hwrm_func_qcaps() and I notice that max_rx_em_flows value is inconsistent. It changes right after port init. max_mac_addrs is also inconsistent because it depends on max_rx_em_flows since commit : http://scm.6wind.com/pub/dpdk.org/dpdk-stable/commit/?h=18.11&id=15f42f5e426d, This is the log I have, when I launch ethtool example application. For port 1, max_rx_em_flows=51116 and then max_rx_em_flows=61292 # ethtool -l 0-1 -n 4 EAL: Detected 12 lcore(s) EAL: Detected 1 NUMA nodes EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Some devices want iova as va but pa will be used because.. EAL: vfio-noiommu mode configured EAL: No free hugepages reported in hugepages-1048576kB EAL: Probing VFIO support... EAL: VFIO support initialized EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles ! EAL: PCI device 0000:00:03.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 1af4:1000 net_virtio EAL: PCI device 0000:00:04.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 14e4:16dc net_bnxt EAL: using IOMMU type 8 (No-IOMMU) bnxt_dev_init(): Broadcom NetXtreme driver bnxt bnxt_hwrm_ver_get(): 1.7.6:20.6.107 bnxt_hwrm_ver_get(): Driver HWRM version: 1.9.2 __bnxt_hwrm_func_qcaps(): !!!!!!!!!!!! bp->max_l2_ctx= 4 + 51116 = 51120 bnxt_dev_init(): bnxt found at mem feb04000, node addr 0x1100800000M EAL: PCI device 0000:00:05.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 14e4:16dc net_bnxt bnxt_hwrm_ver_get(): 1.7.6:20.6.107 bnxt_hwrm_ver_get(): Driver HWRM version: 1.9.2 __bnxt_hwrm_func_qcaps(): !!!!!!!!!!!! bp->max_l2_ctx= 4 + 51116 = 51120 bnxt_dev_init(): bnxt found at mem feb0c000, node addr 0x1100908000M Number of NICs: 2 !!!!!!!!!!!! dev_info.max_mac_addrs= 51120 !!!!!!!!!!!! dev_info.max_mac_addrs= 51120 Init port 0.. __bnxt_hwrm_func_qcaps(): !!!!!!!!!!!! bp->max_l2_ctx= 4 + 1 = 5 !!!!!!!!!!!! dev_info.max_mac_addrs= 5 bnxt_print_link_info(): Port 0 Link Down bnxt_print_link_info(): Port 0 Link Up - speed 10000 Mbps - full-duplex Init port 1.. __bnxt_hwrm_func_qcaps(): !!!!!!!!!!!! bp->max_l2_ctx= 4 + 61292 = 61296 !!!!!!!!!!!! dev_info.max_mac_addrs= 61296 bnxt_print_link_info(): Port 1 Link Down bnxt_print_link_info(): Port 1 Link Up - speed 10000 Mbps - full-duplex EthApp> On master, I see that the new calculation for the number of L2 context has been restricted to Whitney chip family. Anyone knows if the chip/FW I am using is compatible with this new calculation ? By the way, I tried to upgrade to FW 214.0.253.5 and Init is falling very early: bnxt_hwrm_func_resc_qcaps(): error 1:0:00000000:00f9 bnxt_dev_init(): hwrm query capability failure rc: ffffffea EAL: Requested device 0000:00:04.0 cannot be used Best Regards Chris