From: Thomas Monjalon <thomas@monjalon.net>
To: Vipin Varghese <vipin.varghese@amd.com>
Cc: dev@dpdk.org, Neerav.Parikh@amd.com, Ferruh.Yigit@amd.com,
Clinton.France@amd.com
Subject: Re: [RFC] doc/linux_gsg: add amd configuration section
Date: Tue, 16 Jan 2024 16:14:15 +0100 [thread overview]
Message-ID: <1893718.tdWV9SEqCh@thomas> (raw)
In-Reply-To: <20231010153409.1701-1-vipin.varghese@amd.com>
There was no comment on this doc.
It is RFC, is it ready to merge?
Instead of the Linux guide, should we add it to the platform guides?
doc/guides/platform/
We may want to create an entry in MAINTAINERS as well.
More details below.
10/10/2023 17:34, Vipin Varghese:
> Add AMD EPYC SoC tuning guide as new setcion of linux getting
typo: section
> started guide.
>
> Signed-off-by: Vipin Varghese <vipin.varghese@amd.com>
> ---
> +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.
Numa -> NUMA
> +
> +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.
Please start a new sentence on a new line.
next prev parent reply other threads:[~2024-01-16 15:14 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
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 [this message]
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=1893718.tdWV9SEqCh@thomas \
--to=thomas@monjalon.net \
--cc=Clinton.France@amd.com \
--cc=Ferruh.Yigit@amd.com \
--cc=Neerav.Parikh@amd.com \
--cc=dev@dpdk.org \
--cc=vipin.varghese@amd.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).