I meant to say "supported in the 23.03 release." just now in my email. sorry for the typo! On Fri, Feb 10, 2023 at 4:43 PM Shepard Siegel < shepard.siegel@atomicrules.com> wrote: > Yes, exactly, the 1d6c:1022 device is the new FX2 device that will be > supported in the 22.03 release. > > -Shep > > > > On Fri, Feb 10, 2023 at 4:11 PM Ferruh Yigit wrote: > >> On 2/10/2023 9:03 PM, Shepard Siegel wrote: >> > Hi Ferruh, >> > The new FX2 device *is* supported by the ark driver as of DPDK 23.03. >> > These changes bring the ark doc up to date for the upcoming release. >> >> I don't know what exactly 'FX2' device is, but I was referring to >> '1d6c:1022' device id. >> Following is the device table from latest code [1], is '1d6c:1022' >> supported? >> >> static const struct rte_pci_id pci_id_ark_map[] = { >> {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x100d)}, >> {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x100e)}, >> {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x100f)}, >> {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1010)}, >> {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1017)}, >> {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1018)}, >> {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1019)}, >> {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101a)}, >> {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101b)}, >> {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101c)}, >> {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101e)}, >> {RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101f)}, >> {.vendor_id = 0, /* sentinel */ }, >> }; >> >> [1] >> >> https://elixir.bootlin.com/dpdk/v22.11.1/source/drivers/net/ark/ark_ethdev.c#L89 >> >> > -Shep >> > >> > >> > On Fri, Feb 10, 2023 at 3:34 PM Ferruh Yigit > > > wrote: >> > >> > On 2/10/2023 7:38 PM, Shepard Siegel wrote: >> > > Include introduced FX2 PCIe ID and description. >> > > >> > > Signed-off-by: Shepard Siegel > > > >> > > --- >> > > doc/guides/nics/ark.rst | 20 ++++++++++++++++++++ >> > > 1 file changed, 20 insertions(+) >> > > >> > > diff --git a/doc/guides/nics/ark.rst b/doc/guides/nics/ark.rst >> > > index ba00f14e80..39cd75064d 100644 >> > > --- a/doc/guides/nics/ark.rst >> > > +++ b/doc/guides/nics/ark.rst >> > > @@ -52,6 +52,10 @@ board. While specific capabilities such as >> > number of physical >> > > hardware queue-pairs are negotiated; the driver is designed to >> > > remain constant over a broad and extendable feature set. >> > > >> > > +* FPGA Vendors Supported: AMD/Xilinx and Intel >> > > +* Number of RX/TX Queue-Pairs: up to 128 >> > > +* PCIe Endpoint Technology: Gen3, Gen4, Gen5 >> > > + >> > > Intentionally, Arkville by itself DOES NOT provide common NIC >> > > capabilities such as offload or receive-side scaling (RSS). >> > > These capabilities would be viewed as a gate-level "tax" on >> > > @@ -302,6 +306,20 @@ ARK PMD supports the following Arkville RTL >> > PCIe instances including: >> > > * ``1d6c:101c`` - AR-ARK-SRIOV-VF [Arkville Virtual Function] >> > > * ``1d6c:101e`` - AR-ARKA-FX1 [Arkville 64B DPDK Data Mover for >> > Agilex R-Tile] >> > > * ``1d6c:101f`` - AR-TK242 [2x100GbE Packet Capture Device] >> > > +* ``1d6c:1022`` - AR-ARKA-FX2 [Arkville 128B DPDK Data Mover for >> > Agilex] >> > >> > Hi Shepard, Ed, >> > >> > This device is not supported by ark driver, am I missing something? >> > >> > > + >> > > +Arkville RTL Core Configurations >> > > +------------------------------------- >> > > + >> > > +Arkville's RTL core may be configured by the user for three >> different >> > > +datapath widths to balance throughput against FPGA logic area. >> > The ARK PMD >> > > +has introspection on the RTL core configuration and acts >> accordingly. >> > > +All three configurations present identical RTL user-facing AXI >> stream >> > > +interfaces for both AMD/Xilinx and Intel FPGAs. >> > > + >> > > +* ARK-FX0 - 256-bit 32B datapath (PCIe Gen3, Gen4) >> > > +* ARK-FX1 - 512-bit 64B datapath (PCIe Gen3, Gen4, Gen5) >> > > +* ARK-FX2 - 1024-bit 128B datapath (PCIe Gen5x16 Only) >> > > >> > > DPDK and Arkville Firmware Versioning >> > > ------------------------------------- >> > > @@ -334,6 +352,8 @@ Supported Features >> > > ------------------ >> > > >> > > * Dynamic ARK PMD extensions >> > > +* Dynamic per-queue MBUF (re)sizing up to 32KB >> > > +* SR-IOV, VF-based queue-segregation >> > > * Multiple receive and transmit queues >> > > * Jumbo frames up to 9K >> > > * Hardware Statistics >> > >> >>