From: "Dey, Souvik" <sodey@rbbn.com>
To: "harish.patil@cavium.com" <harish.patil@cavium.com>,
"rasesh.mody@cavium.com" <rasesh.mody@cavium.com>,
"shahed.shaikh@cavium.com" <shahed.shaikh@cavium.com>,
Rasesh Mody <rmody@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] net/bnx2x: Qlogic nic card support (1077:16a1)
Date: Mon, 5 Oct 2020 18:13:57 +0000 [thread overview]
Message-ID: <DM6PR03MB47779366B72F48E0A339614ACD0C0@DM6PR03MB4777.namprd03.prod.outlook.com> (raw)
Hi All,
I see that the linux bnx2x driver supports the following vendor id : device id
* vendor: 1077 ("QLogic Corp."), device: 16a1
* vendor: 1077 ("QLogic Corp."), device: 16a4
* vendor: 1077 ("QLogic Corp."), device: 16ad
but this are not supported by the bnx2x_pmd. This combination is not even supported by the qede_pmd. Does this mean that this device is not supported by dpdk even though linux driver supports it ? I am currently using 18.11.10 dpdk version but did check the latest code too and don't see this devices supported. Can you please update me on this. We are trying to using the HPE FlxFbrc 10Gb 4p 536FLR-T Adptr( specs<https://h20195.www2.hpe.com/v2/GetPDF.aspx/c04939487.pdfQuickSpecs>), the 57840S 10 Gb Ethernet controller f in a PCIe 3.0 compliant form factor designed for HPE ProLiant servers.
lspci -nnn | grep Ether
04:00.0 Ethernet controller [0200]: QLogic Corp. Device [1077:16a1] (rev 11)
04:00.1 Ethernet controller [0200]: QLogic Corp. Device [1077:16a1] (rev 11)
04:00.2 Ethernet controller [0200]: QLogic Corp. Device [1077:16a1] (rev 11)
04:00.3 Ethernet controller [0200]: QLogic Corp. Device [1077:16a1] (rev 11)
04:01.0 Ethernet controller [0200]: QLogic Corp. Device [1077:16ad]
04:01.1 Ethernet controller [0200]: QLogic Corp. Device [1077:16ad]
04:01.2 Ethernet controller [0200]: QLogic Corp. Device [1077:16ad]
04:01.3 Ethernet controller [0200]: QLogic Corp. Device [1077:16ad]
Kernel code :
drivers<https://elixir.bootlin.com/linux/latest/source/drivers>/net<https://elixir.bootlin.com/linux/latest/source/drivers/net>/ethernet<https://elixir.bootlin.com/linux/latest/source/drivers/net/ethernet>/broadcom<https://elixir.bootlin.com/linux/latest/source/drivers/net/ethernet/broadcom>/bnx2x<https://elixir.bootlin.com/linux/latest/source/drivers/net/ethernet/broadcom/bnx2x>/bnx2x_main.c<https://elixir.bootlin.com/linux/latest/source/drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c>
{ PCI_VDEVICE<https://elixir.bootlin.com/linux/latest/C/ident/PCI_VDEVICE>(BROADCOM, PCI_DEVICE_ID_NX2_57840_4_10<https://elixir.bootlin.com/linux/latest/C/ident/PCI_DEVICE_ID_NX2_57840_4_10>), BCM57840_4_10<https://elixir.bootlin.com/linux/latest/C/ident/BCM57840_4_10> },
{ PCI_VDEVICE<https://elixir.bootlin.com/linux/latest/C/ident/PCI_VDEVICE>(QLOGIC<https://elixir.bootlin.com/linux/latest/C/ident/QLOGIC>, PCI_DEVICE_ID_NX2_57840_4_10<https://elixir.bootlin.com/linux/latest/C/ident/PCI_DEVICE_ID_NX2_57840_4_10>), BCM57840_4_10<https://elixir.bootlin.com/linux/latest/C/ident/BCM57840_4_10> },
{ PCI_VDEVICE<https://elixir.bootlin.com/linux/latest/C/ident/PCI_VDEVICE>(BROADCOM, PCI_DEVICE_ID_NX2_57840_MF<https://elixir.bootlin.com/linux/latest/C/ident/PCI_DEVICE_ID_NX2_57840_MF>), BCM57840_MF<https://elixir.bootlin.com/linux/latest/C/ident/BCM57840_MF> },
{ PCI_VDEVICE<https://elixir.bootlin.com/linux/latest/C/ident/PCI_VDEVICE>(QLOGIC<https://elixir.bootlin.com/linux/latest/C/ident/QLOGIC>, PCI_DEVICE_ID_NX2_57840_MF<https://elixir.bootlin.com/linux/latest/C/ident/PCI_DEVICE_ID_NX2_57840_MF>), BCM57840_MF<https://elixir.bootlin.com/linux/latest/C/ident/BCM57840_MF> },
{ PCI_VDEVICE<https://elixir.bootlin.com/linux/latest/C/ident/PCI_VDEVICE>(BROADCOM, PCI_DEVICE_ID_NX2_57840_VF<https://elixir.bootlin.com/linux/latest/C/ident/PCI_DEVICE_ID_NX2_57840_VF>), BCM57840_VF<https://elixir.bootlin.com/linux/latest/C/ident/BCM57840_VF> },
{ PCI_VDEVICE<https://elixir.bootlin.com/linux/latest/C/ident/PCI_VDEVICE>(QLOGIC<https://elixir.bootlin.com/linux/latest/C/ident/QLOGIC>, PCI_DEVICE_ID_NX2_57840_VF<https://elixir.bootlin.com/linux/latest/C/ident/PCI_DEVICE_ID_NX2_57840_VF>), BCM57840_VF<https://elixir.bootlin.com/linux/latest/C/ident/BCM57840_VF> },
DPDK code:
net/bnx2x_ethdev.c
{ RTE_PCI_DEVICE(BROADCOM_PCI_VENDOR_ID, CHIP_NUM_57840_4_10) },
{ RTE_PCI_DEVICE(BROADCOM_PCI_VENDOR_ID, CHIP_NUM_57840_MF) },
{ RTE_PCI_DEVICE(BROADCOM_PCI_VENDOR_ID, CHIP_NUM_57840_VF) },
Are we missing the vendor id in the dpdk code which is causing this or there are more changes required to support this card ?
Thanks in advance for the help. Racing against time to support this card, so any prompt reply will be highly appreciated.
--
Regards,
Souvik
reply other threads:[~2020-10-05 18:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=DM6PR03MB47779366B72F48E0A339614ACD0C0@DM6PR03MB4777.namprd03.prod.outlook.com \
--to=sodey@rbbn.com \
--cc=dev@dpdk.org \
--cc=harish.patil@cavium.com \
--cc=rasesh.mody@cavium.com \
--cc=rmody@marvell.com \
--cc=shahed.shaikh@cavium.com \
/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).