From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id A184A41C8B; Mon, 13 Feb 2023 18:09:35 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8B2F842D10; Mon, 13 Feb 2023 18:09:35 +0100 (CET) Received: from mail-ed1-f51.google.com (mail-ed1-f51.google.com [209.85.208.51]) by mails.dpdk.org (Postfix) with ESMTP id BF24440EE4 for ; Mon, 13 Feb 2023 18:09:34 +0100 (CET) Received: by mail-ed1-f51.google.com with SMTP id cq19so11134661edb.5 for ; Mon, 13 Feb 2023 09:09:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=atomicrules-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=efbKal4L1oKflD2FHAQ1VQJ3ghxcP3r5fI9gPnnbNQc=; b=F96ncY6P1eHm+hhjRzebXVjIstm3A16uNdR1jzku+LpDCw0OwPrZSN56SReyIOn2KM sT3XbjuEgxjKCs71h8DxG16b/UKwE8IezdlWaD/XlOKUQuVxRjcvapiAr0CbUOIvAdDO QgJ9cfh9YCdU/5SQ+n6k9+6GQoQR2B0HtDXQrSzLsIkC+XWh9++/Mzr/DZNIt+TItXFa pB0aeVtOULJ4O1FqE/6h/v/JurSybl+2NKAjq9+qG5GQWft+n7efxq2C4XV319BROkDU Ow5pK4E1o9LW7AKVE6dDdDT/Oo2TZRd/dNeK0Dqs4nCtGi6G/JV5ipNhTois3TLWl+lf WY8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=efbKal4L1oKflD2FHAQ1VQJ3ghxcP3r5fI9gPnnbNQc=; b=ipc5sWaXW3SH2AZ8B2Et+Qs/xsPlUy3lzAm7WiAPQl8qvhAcNapFPEjpbdMYOedqJ7 cqIdvzgEq6fPG5kXMRcIeUUJ2VbjDdtJpz6xsgjOji+SaVqF9q4L0mmjKu+6bsexITfu UOAe5d2DxZk+i/uqFcbf7miBZeBpZFDCucJGqYsjkxO9yXGXmbEGkxIEDigyUP/oogWu Zc4UJmGMffbEX1jP/7zl0m/dqfkfb/l9CJabUbZRY1GcbAWvQtMdWM30Zi1wapMSs5kF eBAkjH8k+vDocw7NaDTSCpJyFsusV5vvLZnD5U/+hbDayuT5hxkUlGmXbp1FhvD6eOIY ycbA== X-Gm-Message-State: AO0yUKUICUJR5rL22vzqPr1I9CeBFM0X1PuzK3/xExc59o3ww0eRz1WI /l9IScyoumb580OGdsrUQViGLrQUhbYo5DYMlM0U6RpfdK5spg== X-Google-Smtp-Source: AK7set/Gyn07G3u8iF/7SmAwjUacA067YTrI6smGYk0SG4y6DDbyme/rohIH9IhoghrfTHWUrUxPZb8rwz8mchKnjdA= X-Received: by 2002:a50:a41d:0:b0:4ac:50e4:1eee with SMTP id u29-20020a50a41d000000b004ac50e41eeemr4025117edb.3.1676308174467; Mon, 13 Feb 2023 09:09:34 -0800 (PST) MIME-Version: 1.0 References: <20230211141459.2857045-1-shepard.siegel@atomicrules.com> <20230213145824.2886910-1-shepard.siegel@atomicrules.com> In-Reply-To: From: Shepard Siegel Date: Mon, 13 Feb 2023 12:09:23 -0500 Message-ID: Subject: Re: [PATCH 1/4] doc: clarify the existing net/ark guide To: Ferruh Yigit Cc: ed.czeck@atomicrules.com, dev@dpdk.org Content-Type: multipart/alternative; boundary="0000000000004602fe05f497e948" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --0000000000004602fe05f497e948 Content-Type: text/plain; charset="UTF-8" Hi Ferruh, Yes, there will probably be next versions in the future. If you don't mind making the marker length adjustment, that would be great. Regarding MBUF (re)sizing - Arkville supports the ability to configure or reconfigure the MBUF size used on a per-queue basis. This feature is useful when the are conflicting motivations for using smaller/larger MBUF sizes. For example, user can switch a queue to use a size best for that queue's application workload. -Shep On Mon, Feb 13, 2023 at 10:46 AM Ferruh Yigit wrote: > On 2/13/2023 2:58 PM, Shepard Siegel wrote: > > Add detail for the existing Arkville configurations FX0 and FX1. > > Corrected minor errors of omission. > > > > Signed-off-by: Shepard Siegel > > --- > > doc/guides/nics/ark.rst | 18 ++++++++++++++++++ > > 1 file changed, 18 insertions(+) > > > > diff --git a/doc/guides/nics/ark.rst b/doc/guides/nics/ark.rst > > index ba00f14e80..edaa02dc96 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 > > @@ -303,6 +307,18 @@ ARK PMD supports the following Arkville RTL PCIe > instances including: > > * ``1d6c:101e`` - AR-ARKA-FX1 [Arkville 64B DPDK Data Mover for Agilex > R-Tile] > > * ``1d6c:101f`` - AR-TK242 [2x100GbE Packet Capture Device] > > > > +Arkville RTL Core Configurations > > +------------------------------------- > > + > > The title marker length (-) should be same as title length, can you > please fix if there will be next version, if not I can fix while merging. > > > > +Arkville's RTL core may be configured by the user with different > > +datapath widths to balance throughput against FPGA logic area. The ARK > PMD > > +has introspection on the RTL core configuration and acts accordingly. > > +All Arkville 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) > > + > > DPDK and Arkville Firmware Versioning > > ------------------------------------- > > > > @@ -334,6 +350,8 @@ Supported Features > > ------------------ > > > > * Dynamic ARK PMD extensions > > +* Dynamic per-queue MBUF (re)sizing up to 32KB > > What is this feature? What does it mean to size/resize mbuf dynamically? > > > +* SR-IOV, VF-based queue-segregation > > * Multiple receive and transmit queues > > * Jumbo frames up to 9K > > * Hardware Statistics > > --0000000000004602fe05f497e948 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Ferruh,

Yes, there will probably be = next versions in the future. If you don't mind making the marker length= adjustment, that would be great.

Regarding MBUF (= re)sizing=C2=A0 - Arkville supports the=C2=A0ability to configure or reconf= igure the MBUF size used on a per-queue basis. This feature=C2=A0is useful = when the are conflicting motivations for using smaller/larger MBUF sizes. F= or example, user can switch a queue to use a size best for that queue's= =C2=A0application workload.

-Shep


On Mon, Feb 13, 2023 at 10:46 AM Ferruh Yigit <ferruh.yigit@amd.com> wrote:
On 2/13/2023 2:58 PM, Shepard Siegel= wrote:
> Add detail for the existing Arkville configurations FX0 and FX1.
> Corrected minor errors of omission.
>
> Signed-off-by: Shepard Siegel <shepard.siegel@atomicrules.com>
> ---
>=C2=A0 doc/guides/nics/ark.rst | 18 ++++++++++++++++++
>=C2=A0 1 file changed, 18 insertions(+)
>
> diff --git a/doc/guides/nics/ark.rst b/doc/guides/nics/ark.rst
> index ba00f14e80..edaa02dc96 100644
> --- a/doc/guides/nics/ark.rst
> +++ b/doc/guides/nics/ark.rst
> @@ -52,6 +52,10 @@ board. While specific capabilities such as number o= f physical
>=C2=A0 hardware queue-pairs are negotiated; the driver is designed to >=C2=A0 remain constant over a broad and extendable feature set.
>=C2=A0
> +* FPGA Vendors Supported: AMD/Xilinx and Intel
> +* Number of RX/TX Queue-Pairs: up to 128
> +* PCIe Endpoint Technology: Gen3, Gen4, Gen5
> +
>=C2=A0 Intentionally, Arkville by itself DOES NOT provide common NIC >=C2=A0 capabilities such as offload or receive-side scaling (RSS).
>=C2=A0 These capabilities would be viewed as a gate-level "tax&quo= t; on
> @@ -303,6 +307,18 @@ ARK PMD supports the following Arkville RTL PCIe = instances including:
>=C2=A0 * ``1d6c:101e`` - AR-ARKA-FX1 [Arkville 64B DPDK Data Mover for = Agilex R-Tile]
>=C2=A0 * ``1d6c:101f`` - AR-TK242 [2x100GbE Packet Capture Device]
>=C2=A0
> +Arkville RTL Core Configurations
> +-------------------------------------
> +

The title marker length (-) should be same as title length, can you
please fix if there will be next version, if not I can fix while merging.

> +Arkville's RTL core may be configured by the user with different<= br> > +datapath widths to balance throughput against FPGA logic area. The AR= K PMD
> +has introspection on the RTL core configuration and acts accordingly.=
> +All Arkville configurations present identical RTL user-facing AXI str= eam
> +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)
> +
>=C2=A0 DPDK and Arkville Firmware Versioning
>=C2=A0 -------------------------------------
>=C2=A0
> @@ -334,6 +350,8 @@ Supported Features
>=C2=A0 ------------------
>=C2=A0
>=C2=A0 * Dynamic ARK PMD extensions
> +* Dynamic per-queue MBUF (re)sizing up to 32KB

What is this feature? What does it mean to size/resize mbuf dynamically?
> +* SR-IOV, VF-based queue-segregation
>=C2=A0 * Multiple receive and transmit queues
>=C2=A0 * Jumbo frames up to 9K
>=C2=A0 * Hardware Statistics

--0000000000004602fe05f497e948--