From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 6/6] fzsync: Check processor affinity
Date: Mon, 8 Mar 2021 15:53:32 +0100 [thread overview]
Message-ID: <YEY6bJ/FYL240kK9@yuki.lan> (raw)
In-Reply-To: <20210305155123.18199-7-rpalethorpe@suse.com>
Hi!
> It is useful for testing Fuzzy Sync itself to set the CPU affinity to
> a single core. The current processes affinity does not effect
^
affect?
> tst_ncpus(), but we can get the affinity separately.
>
> Note that checking this still does not guarantee we will use yield
> when restricted to only one core. We would have to periodically probe
> which CPUs threads are running on until we detect more than one CPU.
>
> Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
> ---
> include/tst_fuzzy_sync.h | 20 ++++++++++++++++++--
> 1 file changed, 18 insertions(+), 2 deletions(-)
>
> diff --git a/include/tst_fuzzy_sync.h b/include/tst_fuzzy_sync.h
> index 36a604e13..ea356ab44 100644
> --- a/include/tst_fuzzy_sync.h
> +++ b/include/tst_fuzzy_sync.h
> @@ -59,9 +59,11 @@
> * @sa tst_fzsync_pair
> */
>
> +#define _GNU_SOURCE
> +
> #include <math.h>
> #include <pthread.h>
> -#include <sched.h>
> +#include "lapi/cpuset.h"
> #include <stdbool.h>
> #include <stdlib.h>
> #include <sys/time.h>
> @@ -213,12 +215,26 @@ struct tst_fzsync_pair {
> */
> static void tst_fzsync_pair_init(struct tst_fzsync_pair *pair)
> {
> + long ncpus = tst_ncpus();
> +#ifdef CPU_COUNT
> + size_t cpusz = CPU_ALLOC_SIZE(ncpus);
> + cpu_set_t *cpus = CPU_ALLOC(ncpus);
> +
> + if (sched_getaffinity(0, cpusz, cpus)) {
> + tst_res(TWARN | TERRNO, "sched_getaffinity(0, %zu, %zx)",
> + cpusz, (size_t)cpus);
> + } else {
> + ncpus = CPU_COUNT(cpus);
> + }
> + free(cpus);
> +#endif
Can we instead put this into the lib/tst_cpu.c and call it
tst_allowed_cpus() or something like this?
> CHK(avg_alpha, 0, 1, 0.25);
> CHK(min_samples, 20, INT_MAX, 1024);
> CHK(max_dev_ratio, 0, 1, 0.1);
> CHK(exec_time_p, 0, 1, 0.5);
> CHK(exec_loops, 20, INT_MAX, 3000000);
> - CHK(yield_in_wait, 0, 1, (tst_ncpus() <= 1));
> + CHK(yield_in_wait, 0, 1, (ncpus <= 1));
> }
> #undef CHK
>
> --
> 2.30.1
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2021-03-08 14:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 15:51 [LTP] [PATCH 0/6] Fuzzy Sync yielding and validation test Richard Palethorpe
2021-03-05 15:51 ` [LTP] [PATCH 1/6] fzsync: Add self test Richard Palethorpe
2021-03-08 15:30 ` Cyril Hrubis
2021-03-08 16:18 ` Richard Palethorpe
2021-03-05 15:51 ` [LTP] [PATCH 2/6] fzsync: Reset delay bias Richard Palethorpe
2021-03-08 14:16 ` Cyril Hrubis
2021-03-08 14:50 ` Richard Palethorpe
2021-03-05 15:51 ` [LTP] [PATCH 3/6] fzsync: Correctly print positive lower delay range bound Richard Palethorpe
2021-03-08 14:18 ` Cyril Hrubis
2021-03-05 15:51 ` [LTP] [PATCH 4/6] fzsync: Add sched_yield for single core machine Richard Palethorpe
2021-03-05 15:51 ` [LTP] [PATCH 5/6] fzsync: Move yield check out of loop and add yield to delay Richard Palethorpe
2021-03-08 11:32 ` Leo Liang
2021-03-08 14:48 ` Cyril Hrubis
2021-03-05 15:51 ` [LTP] [PATCH 6/6] fzsync: Check processor affinity Richard Palethorpe
2021-03-08 11:33 ` Leo Liang
2021-03-08 14:53 ` Cyril Hrubis [this message]
2021-03-08 15:30 ` Richard Palethorpe
2021-03-09 13:45 ` [LTP] [PATCH 0/6] Fuzzy Sync yielding and validation test Petr Vorel
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=YEY6bJ/FYL240kK9@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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