From: "Varghese, Vipin" <vipin.varghese@amd.com>
To: Thomas Monjalon <thomas@monjalon.net>
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: Wed, 24 Jan 2024 23:41:20 +0530 [thread overview]
Message-ID: <c9ab40d5-d0bf-4963-90df-aaa26823401d@amd.com> (raw)
In-Reply-To: <1893718.tdWV9SEqCh@thomas>
[-- Attachment #1: Type: text/plain, Size: 2290 bytes --]
On 1/16/2024 8:44 PM, Thomas Monjalon wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> There was no comment on this doc.
> It is RFC, is it ready to merge?
new patch shared doc/linux_gsg: add amd configuration section -
Patchwork (dpdk.org)
<https://patchwork.dpdk.org/project/dpdk/patch/20240124181021.1759-1-vipin.varghese@amd.com/>
>
> 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.
thank you, added the same under `AMD x86`
>
> More details below.
>
>
> 10/10/2023 17:34, Vipin Varghese:
>> Add AMD EPYC SoC tuning guide as new setcion of linux getting
> typo: section
fixed, spell check did not catch this for me. My mistake
>> 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
changed to all capital
>> +
>> +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.
correction applied.
>
[-- Attachment #2: Type: text/html, Size: 4359 bytes --]
next prev parent reply other threads:[~2024-01-24 18:11 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
2024-01-24 18:11 ` Varghese, Vipin [this message]
-- 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=c9ab40d5-d0bf-4963-90df-aaa26823401d@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 \
--cc=thomas@monjalon.net \
/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).