From: Shepard Siegel <shepard.siegel@atomicrules.com>
To: ed.czeck@atomicrules.com
Cc: dev@dpdk.org, Shepard Siegel <shepard.siegel@atomicrules.com>
Subject: [PATCH v3 2/2] doc: add Arkville FX2 PCIe device description
Date: Fri, 10 Feb 2023 20:26:59 -0500 [thread overview]
Message-ID: <20230211012659.2611391-2-shepard.siegel@atomicrules.com> (raw)
In-Reply-To: <20230211012659.2611391-1-shepard.siegel@atomicrules.com>
Update net/ark guide for clarity.
Include list of FX0, FX1 and FX2 PCIe devices.
Signed-off-by: Shepard Siegel <shepard.siegel@atomicrules.com>
---
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]
+
+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
--
2.25.1
next prev parent reply other threads:[~2023-02-11 1:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 19:38 [PATCH] doc: update ark guide Shepard Siegel
2023-02-10 20:34 ` Ferruh Yigit
2023-02-10 21:03 ` Shepard Siegel
2023-02-10 21:10 ` Ferruh Yigit
2023-02-10 21:43 ` Shepard Siegel
2023-02-10 21:46 ` Shepard Siegel
2023-02-10 22:35 ` [PATCH v2] " Shepard Siegel
2023-02-10 22:56 ` Ferruh Yigit
2023-02-10 23:47 ` Shepard Siegel
2023-02-11 1:26 ` [PATCH v3 1/2] net/ark: introduce Arkville FX2 PCIe device Shepard Siegel
2023-02-11 1:26 ` Shepard Siegel [this message]
2023-02-11 2:13 ` [PATCH v3 2/2] doc: add Arkville FX2 PCIe device description Ferruh Yigit
2023-02-11 3:07 ` Shepard Siegel
2023-02-13 12:07 ` Ferruh Yigit
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=20230211012659.2611391-2-shepard.siegel@atomicrules.com \
--to=shepard.siegel@atomicrules.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.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).