From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Shaopeng Tan <tan.shaopeng@jp.fujitsu.com>
Subject: Re: [PATCH 5/7] selftests/resctrl: Use pointers to build benchmark cmd and make it const
Date: Thu, 17 Aug 2023 11:32:28 +0300 (EEST) [thread overview]
Message-ID: <c8b7118c-5830-98a0-5ae-66072e384b3@linux.intel.com> (raw)
In-Reply-To: <bacc2e6f-f747-ec65-b23b-4275d1cac018@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3100 bytes --]
On Wed, 16 Aug 2023, Reinette Chatre wrote:
> On 8/16/2023 12:13 AM, Ilpo Järvinen wrote:
> > On Tue, 15 Aug 2023, Reinette Chatre wrote:
> >> On 8/15/2023 2:42 AM, Ilpo Järvinen wrote:
> >>> On Mon, 14 Aug 2023, Reinette Chatre wrote:
> >>>>
> >>>> On 8/8/2023 2:16 AM, Ilpo Järvinen wrote:
>
> ...
> >>>>> diff --git a/tools/testing/selftests/resctrl/resctrl.h b/tools/testing/selftests/resctrl/resctrl.h
> >>>>> index bcd0d2060f81..ddb1e83a3a64 100644
> >>>>> --- a/tools/testing/selftests/resctrl/resctrl.h
> >>>>> +++ b/tools/testing/selftests/resctrl/resctrl.h
> >>>>> @@ -6,6 +6,7 @@
> >>>>> #include <math.h>
> >>>>> #include <errno.h>
> >>>>> #include <sched.h>
> >>>>> +#include <stdint.h>
> >>>>> #include <stdlib.h>
> >>>>> #include <unistd.h>
> >>>>> #include <string.h>
> >>>>> @@ -38,7 +39,14 @@
> >>>>>
> >>>>> #define END_OF_TESTS 1
> >>>>>
> >>>>> +#define BENCHMARK_ARGS 64
> >>>>> +
> >>>>> +/* Approximate %zu max length */
> >>>>> +#define SIZE_MAX_DECIMAL_SIZE (sizeof(SIZE_MAX) * 8 / 3 + 2)
> >>>>> +
> >>>>> +/* Define default span both as integer and string, these should match */
> >>>>> #define DEFAULT_SPAN (250 * MB)
> >>>>> +#define DEFAULT_SPAN_STR "262144000"
> >>>>
> >>>> I think above hardcoding can be eliminated by using asprintf()? This
> >>>> does allocate memory though so I would like to understand why one
> >>>> goal is to not dynamically allocate memory.
> >>>
> >>> Because it's simpler on the _free() side_. If there's no allocation, no
> >>> free() is needed.
> >>>
> >>> Only challenge that remains is the int -> string conversion for the
> >>> default span which can be either done like in the patch or using some
> >>> preprocessor trickery to convert the number to string. If you prefer the
> >>> latter, I can change to that so it's not hardcoded both as int and string.
> >>>
> >>
> >> This manual int->string sounds like the trickery to me and can be avoided
> >> by just using asprintf(). I understand that no free() is needed when no
> >> memory is allocated but it looks to me as though these allocations can
> >> be symmetrical - allocate the memory before the tests are run and free it
> >> after?
> >
> > It could be symmetrical but that means I'll be doing unnecessary alloc if
> > -b is provided which I assume you're against given your comment on always
> > creating copy of cmd in CMT test's case.
>
> I seemed to have lost track here ... could you please elaborate where the
> unnecessary alloc will be?
If there's what you call "symmetry", it implies the code always does
alloc. However, the logic in main() is such that when -b is provided, no
default benchmark command needs to be assigned, so no alloc for span is
necessary. Thus, there either is unnecessary alloc with -b or _no
symmetry_.
But I've already converted to asprintf() so no need to continue this
discussion.
> > I think I'll use similar resolution to this as CMT test does, it has an
> > extra variable which is NULL in when -b is provided so free() is no-op
> > on that path. Then I can use asprintf().
> >
>
> Reinette
>
--
i.
next prev parent reply other threads:[~2023-08-17 8:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 9:16 [PATCH 0/7] selftests/resctrl: Rework benchmark command handling Ilpo Järvinen
2023-08-08 9:16 ` [PATCH 1/7] selftests/resctrl: Ensure the benchmark commands fits to its array Ilpo Järvinen
2023-08-14 17:48 ` Reinette Chatre
2023-08-15 9:10 ` Ilpo Järvinen
2023-08-15 15:47 ` Reinette Chatre
2023-08-16 6:32 ` Ilpo Järvinen
2023-08-16 21:46 ` Reinette Chatre
2023-08-08 9:16 ` [PATCH 2/7] selftests/resctrl: Correct benchmark command help Ilpo Järvinen
2023-08-14 17:49 ` Reinette Chatre
2023-08-15 9:11 ` Ilpo Järvinen
2023-08-08 9:16 ` [PATCH 3/7] selftests/resctrl: Remove bw_report and bm_type from main() Ilpo Järvinen
2023-08-14 17:49 ` Reinette Chatre
2023-08-08 9:16 ` [PATCH 4/7] selftests/resctrl: Simplify span lifetime Ilpo Järvinen
2023-08-14 17:49 ` Reinette Chatre
2023-08-08 9:16 ` [PATCH 5/7] selftests/resctrl: Use pointers to build benchmark cmd and make it const Ilpo Järvinen
2023-08-14 17:50 ` Reinette Chatre
2023-08-15 9:42 ` Ilpo Järvinen
2023-08-15 15:48 ` Reinette Chatre
2023-08-16 7:13 ` Ilpo Järvinen
2023-08-16 21:52 ` Reinette Chatre
2023-08-17 8:32 ` Ilpo Järvinen [this message]
2023-08-17 15:45 ` Reinette Chatre
2023-08-18 7:25 ` Ilpo Järvinen
2023-08-08 9:16 ` [PATCH 6/7] selftests/resctrl: remove ben_count variable Ilpo Järvinen
2023-08-14 17:51 ` Reinette Chatre
2023-08-08 9:16 ` [PATCH 7/7] selftests/resctrl: Cleanup benchmark argument parsing Ilpo Järvinen
2023-08-14 17:56 ` Reinette Chatre
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=c8b7118c-5830-98a0-5ae-66072e384b3@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.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 \
--cc=skhan@linuxfoundation.org \
--cc=tan.shaopeng@jp.fujitsu.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