From: Peter Xu <peterx@redhat.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>,
linux-rt-users@vger.kernel.org,
Pradipta Kumar Sahoo <psahoo@redhat.com>
Subject: Re: [PATCH rt-tests 2/2] oslat: Use cpuset size as upper bound
Date: Wed, 10 Feb 2021 12:14:35 -0500 [thread overview]
Message-ID: <20210210171435.GN103365@xz-x1> (raw)
In-Reply-To: <20210210165407.9770-3-dwagner@suse.de>
On Wed, Feb 10, 2021 at 05:54:07PM +0100, Daniel Wagner wrote:
> To assign the threads to the correct CPU we need to use the cpuset
> size as upper bound for the loop and not the number of threads.
>
> Fixes: 85b0763dacd9 ("oslat: Use parse_cpumask() from rt-numa.h")
> Reported-by: Peter Xu <peterx@redhat.com>
Please instead add:
Reported-by: Pradipta Kumar Sahoo <psahoo@redhat.com>
Pradipta, would you verify and see whether this patch fixes your issue?
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2021-02-10 17:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 16:54 [PATCH rt-tests 0/2] oslat fixes Daniel Wagner
2021-02-10 16:54 ` [PATCH rt-tests 1/2] oslat: Print version string Daniel Wagner
2021-02-10 17:12 ` Peter Xu
2021-02-10 17:28 ` John Kacur
2021-02-10 17:33 ` Daniel Wagner
2021-02-10 17:53 ` Peter Xu
2021-02-10 18:15 ` Daniel Wagner
2021-02-10 19:26 ` Peter Xu
2021-02-10 17:59 ` John Kacur
2021-02-10 18:21 ` Daniel Wagner
2021-02-10 19:12 ` John Kacur
2021-02-11 4:32 ` John Kacur
2021-02-10 16:54 ` [PATCH rt-tests 2/2] oslat: Use cpuset size as upper bound Daniel Wagner
2021-02-10 17:14 ` Peter Xu [this message]
2021-02-11 4:28 ` John Kacur
2021-02-11 15:24 ` Peter Xu
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=20210210171435.GN103365@xz-x1 \
--to=peterx@redhat.com \
--cc=dwagner@suse.de \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=psahoo@redhat.com \
--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).