linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiafei Pan <jiafei.pan@nxp.com>
To: "williams@redhat.com" <williams@redhat.com>,
	"jkacur@redhat.com" <jkacur@redhat.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
	Jiafei Pan <jiafei.pan@nxp.com>
Subject: RE: [PATCH] rt-tests: pi_stress: fix testing threads' smp affinity
Date: Fri, 7 May 2021 06:22:19 +0000	[thread overview]
Message-ID: <AS8PR04MB81825DF5E1C40EEED0C2DC2C8A579@AS8PR04MB8182.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20210326094404.18110-1-Jiafei.Pan@nxp.com>

Any comments? thanks.

Best Regards,
Jiafei.

> -----Original Message-----
> From: Jiafei Pan <jiafei.pan@nxp.com>
> Sent: Friday, March 26, 2021 5:44 PM
> To: williams@redhat.com; jkacur@redhat.com
> Cc: linux-rt-users@vger.kernel.org; Jiafei Pan <jiafei.pan@nxp.com>; Jiafei
> Pan <jiafei.pan@nxp.com>
> Subject: [PATCH] rt-tests: pi_stress: fix testing threads' smp affinity
> 
> This patch includes the following modification:
> 1. Make sure test threads and admin threads don't run on the same CPU
>    Core if uniprocessor is not set or not on single Core platform to
>    avoid starve admin threads.
> 2. Force to use SCHED_RR if more than one Groups running one a CPU
>    Core to avoid test failure because threads in different Groups
>    are using the same priority, SCHED_FIFO which is default policy
>    and it maybe trigger deadlock of testing threads.
> 
> Signed-off-by: Jiafei Pan <Jiafei.Pan@nxp.com>
> ---
>  src/pi_tests/pi_stress.c | 23 +++++++++++++++++++----
>  1 file changed, 19 insertions(+), 4 deletions(-)
> 
> diff --git a/src/pi_tests/pi_stress.c b/src/pi_tests/pi_stress.c index
> 49f89b7..8795908 100644
> --- a/src/pi_tests/pi_stress.c
> +++ b/src/pi_tests/pi_stress.c
> @@ -237,6 +237,13 @@ int main(int argc, char **argv)
>  	/* process command line arguments */
>  	process_command_line(argc, argv);
> 
> +	if (ngroups > (num_processors - 1)) {
> +		printf("Warning: One Core will used for administor thread, the other
> CPU Core will run test thread,\n");
> +		printf("\t it will running more than one Group on one Core (groups >
> num_of_processors -1),\n");
> +		printf("\t it will force to use SCHED_RR, or change groups number to
> be lower than %ld \n", num_processors);
> +		policy = SCHED_RR;
> +	}
> +
>  	/* set default sched attributes */
>  	setup_sched_config(policy);
> 
> @@ -285,9 +292,17 @@ int main(int argc, char **argv)
>  			break;
>  	for (i = 0; i < ngroups; i++) {
>  		groups[i].id = i;
> -		groups[i].cpu = core++;
> -		if (core >= num_processors)
> -			core = 0;
> +		if (num_processors == 1 || uniprocessor) {
> +			groups[i].cpu = 0;
> +		} else {
> +			groups[i].cpu = core;
> +			/* Find next non-admin Core */
> +			do {
> +				core++;
> +				if (core >= num_processors)
> +					core = 0;
> +			} while (CPU_ISSET(core, &admin_cpu_mask));
> +		}
>  		if (create_group(&groups[i]) != SUCCESS)
>  			return FAILURE;
>  	}
> @@ -1143,7 +1158,7 @@ int create_group(struct group_parameters *group)
>  	CPU_ZERO(&mask);
>  	CPU_SET(group->cpu, &mask);
> 
> -	pi_debug("group %d bound to cpu %ld\n", group->id, group->cpu);
> +	printf("group %d bound to cpu %ld\n", group->id, group->cpu);
> 
>  	/* start the low priority thread */
>  	pi_debug("creating low priority thread\n");
> --
> 2.17.1


  reply	other threads:[~2021-05-07  6:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26  9:44 [PATCH] rt-tests: pi_stress: fix testing threads' smp affinity Jiafei Pan
2021-05-07  6:22 ` Jiafei Pan [this message]
2021-05-07 16:01   ` John Kacur
2021-05-08  2:48     ` [EXT] " Jiafei Pan

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=AS8PR04MB81825DF5E1C40EEED0C2DC2C8A579@AS8PR04MB8182.eurprd04.prod.outlook.com \
    --to=jiafei.pan@nxp.com \
    --cc=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=williams@redhat.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;
as well as URLs for NNTP newsgroup(s).