From: "Varghese, Vipin" <vipin.varghese@amd.com>
To: dev@dpdk.org
Cc: Neerav.Parikh@amd.com, Ferruh.Yigit@amd.com, Clinton.France@amd.com
Subject: Re: [RFC] doc/linux_gsg: add amd configuration section
Date: Wed, 20 Dec 2023 14:54:57 +0530 [thread overview]
Message-ID: <9bce5b2f-a283-44da-b04b-d56e9f6df076@amd.com> (raw)
In-Reply-To: <20231010153409.1701-1-vipin.varghese@amd.com>
[-- Attachment #1: Type: text/plain, Size: 3481 bytes --]
Got `Superseded` is there a new version shared for `AMD tuning guide`?
On 10/10/2023 9:04 PM, Vipin Varghese wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> Add AMD EPYC SoC tuning guide as new setcion of linux getting
> started guide.
>
> Signed-off-by: Vipin Varghese<vipin.varghese@amd.com>
> ---
> doc/guides/linux_gsg/amd_platform.rst | 63 +++++++++++++++++++++++++++
> doc/guides/linux_gsg/index.rst | 1 +
> 2 files changed, 64 insertions(+)
> create mode 100644 doc/guides/linux_gsg/amd_platform.rst
>
> diff --git a/doc/guides/linux_gsg/amd_platform.rst b/doc/guides/linux_gsg/amd_platform.rst
> new file mode 100644
> index 0000000000..cdb535e9c0
> --- /dev/null
> +++ b/doc/guides/linux_gsg/amd_platform.rst
> @@ -0,0 +1,63 @@
> +.. SPDX-License-Identifier: BSD-3-Clause
> + Copyright(c) 2023 Advanced Micro Devices, Inc. All rights reserved.
> +
> +How to get best performance on AMD platform
> +===========================================
> +
> +This document shares step-by-step guide for configuring AMD EPYC SoC across various families for getting best performance for DPDK applications.
> +Various factors like BIOS, Numa Per Socket, Memory per Numa, near-far from IO device affects the overall performance.
> +
> +These are covered in various sections of tuning guides shared below.
> +
> +
> +Tuning Guide for AMD EPYC SoC
> +-----------------------------
> +
> +#. `MILAN<https://www.amd.com/content/dam/amd/en/documents/epyc-technical-docs/tuning-guides/data-plane-development-kit-tuning-guide-amd-epyc7003-series-processors.pdf>`_
> +
> +#. `GENOA<https://www.amd.com/content/dam/amd/en/documents/epyc-technical-docs/tuning-guides/58017-amd-epyc-9004-tg-data-plane-dpdk.pdf>`_
> +
> +#. `BERGAMO|SIENNA<https://www.amd.com/content/dam/amd/en/documents/epyc-technical-docs/tuning-guides/58310_amd-epyc-8004-tg-data-plane-dpdk.pdf>`_
> +
> +
> +General Requirements
> +--------------------
> +
> +Memory
> +~~~~~~
> +
> +Refer `Memory Configuration` section for SoC specific details.
> +
> +Note: general thumb rule is to ensure that each memory channel has at least one memory DIMM populated. The ideal memory size for each is at least 8|16|32 GB ECC modules.
> +
> +
> +BIOS
> +----
> +
> +Refer `BIOS Performance` section in tuning guide for recommended settings.
> +
> +
> +Linux Grub
> +----------
> +
> +Refer `Linux OS & Kernel` in tuning guide for recommended settings.
> +
> +
> +NIC and Accelerator
> +-------------------
> +
> +AMD EPYC supports PCIe Generation of 1|2|3|4|5 depending upon SoC families. For best performance ensure the right slots are used which provides adequate bandwidth.
> +
> +Use ``lspci`` to check the speed of a PCI slot ::
> +
> + lspci -s 41:00.0 -vv | grep LnkSta
> +
> + LnkSta: Speed 16GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- ...
> + LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+ ...
> +
> +
> +Compiler
> +-------
> +
> +Refer `Compiler Flags` for recommended version and `-march` flags.
> +
> diff --git a/doc/guides/linux_gsg/index.rst b/doc/guides/linux_gsg/index.rst
> index c3e67bf9ec..ecdaf35eec 100644
> --- a/doc/guides/linux_gsg/index.rst
> +++ b/doc/guides/linux_gsg/index.rst
> @@ -21,3 +21,4 @@ Getting Started Guide for Linux
> linux_eal_parameters
> enable_func
> nic_perf_intel_platform
> + amd_platform
> --
> 2.34.1
>
[-- Attachment #2: Type: text/html, Size: 4893 bytes --]
next prev parent reply other threads:[~2023-12-20 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 15:34 Vipin Varghese
2023-12-20 9:24 ` Varghese, Vipin [this message]
2023-12-20 9:27 ` David Marchand
2023-12-20 9:31 ` Varghese, Vipin
2023-12-20 9:32 ` David Marchand
2023-12-20 9:36 ` Varghese, Vipin
2024-01-16 15:14 ` Thomas Monjalon
2024-01-24 18:11 ` Varghese, Vipin
-- strict thread matches above, loose matches on Subject: below --
2023-10-10 15:25 Vipin Varghese
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=9bce5b2f-a283-44da-b04b-d56e9f6df076@amd.com \
--to=vipin.varghese@amd.com \
--cc=Clinton.France@amd.com \
--cc=Ferruh.Yigit@amd.com \
--cc=Neerav.Parikh@amd.com \
--cc=dev@dpdk.org \
/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).