From: Reinette Chatre <reinette.chatre@intel.com>
To: Swapnil Sapkal <swapnil.sapkal@amd.com>, <tony.luck@intel.com>,
<babu.moger@amd.com>, <fenghua.yu@intel.com>, <shuah@kernel.org>
Cc: <Dave.Martin@arm.com>, <james.morse@arm.com>,
<peternewman@google.com>, <eranian@google.com>,
<tan.shaopeng@fujitsu.com>, <linux-kernel@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>, <x86@kernel.org>
Subject: Re: [PATCH v5 4/5] selftests/resctrl: Use bandwidth values for AMD MBA schemata
Date: Wed, 4 Nov 2026 20:16:05 -0800 [thread overview]
Message-ID: <4f656f59-9f2c-4774-9d9b-3a4d7b7b509d@intel.com> (raw)
In-Reply-To: <e30b8e81-938c-4426-8b4a-2a3a8d5163ad@amd.com>
Hi Swapnil,
On 11/4/26 8:05 PM, Swapnil Sapkal wrote:
> On 29-10-2026 00:15, Reinette Chatre wrote:
>> On 10/22/26 6:25 AM, Swapnil Sapkal wrote:
>>
>>> diff --git a/tools/testing/selftests/resctrl/mba_test.c b/tools/testing/selftests/resctrl/mba_test.c
>>> index 17ae73d3476c..947735e26099 100644
>>> --- a/tools/testing/selftests/resctrl/mba_test.c
>>> +++ b/tools/testing/selftests/resctrl/mba_test.c
>>> @@ -13,10 +13,51 @@
>>> #define RESULT_FILE_NAME "result_mba"
>>> #define NUM_OF_RUNS 5
>>> #define MAX_DIFF_PERCENT 15
>>> +
>>> +/* Intel MBA is specified as a percentage: 10%, 20% ... 100%. */
>>
>> The percentage based interface is the generic interface and not Intel specific.
>> You can drop "Intel" from references to this interface.
>>
>
> Sure, will do.
>
>>> #define ALLOCATION_MAX 100
>>> #define ALLOCATION_MIN 10
>>> #define ALLOCATION_STEP 10
>>> +/*
>>> + * AMD MBA is not a percentage but an absolute memory bandwidth value. The
>>> + * test sweeps the bandwidth from 4 GB/s to 40 GB/s in steps of 4 GB/s,
>>> + * which the hardware represents in units of 1/8 GB/s (i.e. 4 GB/s -> 32,
>>> + * 8 GB/s -> 64, ... 40 GB/s -> 320).
>>> + */
>>> +#define AMD_ALLOCATION_MAX 320
>>
>> The AMD maximum is enumerated from hardware. How can it be ensured this is
>> the appropriate maximum for all AMD systems?
>>
>
> As Babu mentioned, it's difficult for a single-threaded workload to
> reach the hardware-reported value. For that reason, I used these
> values to verify whether throttling takes effect.
Just to confirm, my question was not about needing this value to be the actual
maximum of a system. Instead, I just wanted to confirm that this "320" value that
is hardcoded here for all AMD systems is a _valid_ value. Since the actual maximum
value is enumerated from hardware it is not obvious to me that all systems will support
this hardcoded maximum.
Reinette
next prev parent reply other threads:[~2026-11-05 4:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 13:25 [PATCH v5 0/5] selftests/resctrl: Add MBM and MBA test support for AMD Swapnil Sapkal
2026-10-22 13:25 ` [PATCH v5 1/5] selftests/resctrl: Rename variables and functions to generic names Swapnil Sapkal
2026-10-28 18:38 ` Reinette Chatre
2026-11-03 6:13 ` Swapnil Sapkal
2026-10-22 13:25 ` [PATCH v5 2/5] selftests/resctrl: Detect vendor to select memory controller sysfs name Swapnil Sapkal
2026-10-28 18:39 ` Reinette Chatre
2026-11-03 6:19 ` Swapnil Sapkal
2026-10-22 13:25 ` [PATCH v5 3/5] selftests/resctrl: Add support for MBM and MBA tests on AMD Swapnil Sapkal
2026-10-28 18:41 ` Reinette Chatre
2026-11-03 6:34 ` Swapnil Sapkal
2026-10-22 13:25 ` [PATCH v5 4/5] selftests/resctrl: Use bandwidth values for AMD MBA schemata Swapnil Sapkal
2026-10-28 18:45 ` Reinette Chatre
2026-11-03 1:15 ` Moger, Babu
2026-11-05 4:08 ` Swapnil Sapkal
2026-11-05 4:05 ` Swapnil Sapkal
2026-11-05 4:16 ` Reinette Chatre [this message]
2026-10-22 13:25 ` [PATCH v5 5/5] selftests/resctrl: Enable MBM and MBA tests on AMD Swapnil Sapkal
2026-10-28 18:45 ` Reinette Chatre
2026-11-05 4:16 ` Swapnil Sapkal
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=4f656f59-9f2c-4774-9d9b-3a4d7b7b509d@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=peternewman@google.com \
--cc=shuah@kernel.org \
--cc=swapnil.sapkal@amd.com \
--cc=tan.shaopeng@fujitsu.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®