From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: linux-kselftest@vger.kernel.org, "Shuah Khan" <shuah@kernel.org>,
"Babu Moger" <babu.moger@amd.com>,
"Maciej Wieczór-Retman" <maciej.wieczor-retman@intel.com>,
"Fenghua Yu" <fenghua.yu@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 02/13] selftests/resctrl: Calculate resctrl FS derived mem bw over sleep(1) only
Date: Mon, 25 Mar 2024 15:08:09 +0200 (EET) [thread overview]
Message-ID: <10baa8db-3143-fdd4-49a8-0298db90cc4f@linux.intel.com> (raw)
In-Reply-To: <0910f9ed-2312-46b7-9c64-2982709da3d8@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2071 bytes --]
On Fri, 22 Mar 2024, Reinette Chatre wrote:
> On 3/22/2024 5:11 AM, Ilpo Järvinen wrote:
> > On Tue, 19 Mar 2024, Reinette Chatre wrote:
> >> On 3/11/2024 6:52 AM, Ilpo Järvinen wrote:
> >>> + * Return: = 0 on success. < 0 on failure.
> >>> + */
> >>> +static int get_mem_bw_imc(char *bw_report, float *bw_imc)
> >>> +{
> >>> + float reads, writes, of_mul_read, of_mul_write;
> >>> + int imc, j;
> >>> +
> >>> + /* Start all iMC counters to log values (both read and write) */
> >>> + reads = 0, writes = 0, of_mul_read = 1, of_mul_write = 1;
> >>>
> >>> /*
> >>> * Get results which are stored in struct type imc_counter_config
> >
> >>> @@ -696,7 +725,6 @@ int resctrl_val(const struct resctrl_test *test,
> >>> struct resctrl_val_param *param)
> >>> {
> >>> char *resctrl_val = param->resctrl_val;
> >>> - unsigned long bw_resc_start = 0;
> >>
> >> In the current implementation the first iteration's starting measurement
> >> is, as seen above, 0 ... which makes the first measurement unreliable
> >> and dropped for both the MBA and MBM tests. In this enhancement, the
> >> first measurement is no longer skewed so much so I wonder if this enhancement
> >> can be expanded to the analysis phase where first measurement no longer
> >> needs to be dropped?
> >
> > In ideal world, yes, but I'll have to check the raw numbers. My general
> > feel is that the numbers tend to converge slowly with more iterations
> > being run so the first iteration might still be "off" by quite much (this
> > is definitely the case with CAT tests iterations but I'm not entirely sure
> > any more how it is with other selftests).
>
> >From what I can tell the CAT test is not dropping any results. It looks
> to me that any "settling" is and should be handled in the test before
> the data collection starts.
It doesn't, but the "settling" is there in the raw numbers. I've
considered adding warm-up test(s) before the actual runs to improve the
situation but there's just so many thing still to do...
--
i.
next prev parent reply other threads:[~2024-03-25 13:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 13:52 [PATCH v2 00/13] selftests/resctrl: resctrl_val() related cleanups & improvements Ilpo Järvinen
2024-03-11 13:52 ` [PATCH v2 01/13] selftests/resctrl: Convert get_mem_bw_imc() fd close to for loop Ilpo Järvinen
2024-03-20 4:50 ` Reinette Chatre
2024-03-22 11:59 ` Ilpo Järvinen
2024-03-22 12:00 ` Ilpo Järvinen
2024-03-11 13:52 ` [PATCH v2 02/13] selftests/resctrl: Calculate resctrl FS derived mem bw over sleep(1) only Ilpo Järvinen
2024-03-20 4:53 ` Reinette Chatre
2024-03-22 12:11 ` Ilpo Järvinen
2024-03-22 17:44 ` Reinette Chatre
2024-03-25 13:08 ` Ilpo Järvinen [this message]
2024-03-11 13:52 ` [PATCH v2 03/13] selftests/resctrl: Consolidate get_domain_id() into resctrl_val() Ilpo Järvinen
2024-03-11 13:52 ` [PATCH v2 04/13] selftests/resctrl: Use correct type for pids Ilpo Järvinen
2024-03-11 13:52 ` [PATCH v2 05/13] selftests/resctrl: Cleanup bm_pid and ppid usage & limit scope Ilpo Järvinen
2024-03-11 13:52 ` [PATCH v2 06/13] selftests/resctrl: Rename measure_vals() to measure_mem_bw_vals() & document Ilpo Järvinen
2024-03-11 13:52 ` [PATCH v2 07/13] selftests/resctrl: Add ->measure() callback to resctrl_val_param Ilpo Järvinen
2024-03-11 13:52 ` [PATCH v2 08/13] selftests/resctrl: Add ->init() callback into resctrl_val_param Ilpo Järvinen
2024-03-13 10:15 ` Maciej Wieczor-Retman
2024-03-13 10:28 ` Maciej Wieczor-Retman
2024-03-13 11:37 ` Ilpo Järvinen
2024-03-13 13:53 ` Maciej Wieczor-Retman
2024-03-13 13:59 ` Ilpo Järvinen
2024-03-14 16:07 ` Maciej Wieczor-Retman
2024-03-14 16:09 ` Ilpo Järvinen
2024-03-20 4:58 ` Reinette Chatre
2024-03-22 12:22 ` Ilpo Järvinen
2024-03-11 13:52 ` [PATCH v2 09/13] selftests/resctrl: Simplify bandwidth report type handling Ilpo Järvinen
2024-03-11 13:52 ` [PATCH v2 10/13] selftests/resctrl: Make some strings passed to resctrlfs functions const Ilpo Järvinen
2024-03-11 13:52 ` [PATCH v2 11/13] selftests/resctrl: Convert ctrlgrp & mongrp to pointers Ilpo Järvinen
2024-03-20 15:20 ` Reinette Chatre
2024-03-22 12:30 ` Ilpo Järvinen
2024-03-22 17:44 ` Reinette Chatre
2024-03-25 13:14 ` Ilpo Järvinen
2024-03-11 13:52 ` [PATCH v2 12/13] selftests/resctrl: Remove mongrp from MBA test Ilpo Järvinen
2024-03-11 13:52 ` [PATCH v2 13/13] selftests/resctrl: Remove test name comparing from write_bm_pid_to_resctrl() Ilpo Järvinen
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=10baa8db-3143-fdd4-49a8-0298db90cc4f@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=babu.moger@amd.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=reinette.chatre@intel.com \
--cc=shuah@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