From: Daniel Wagner <wagi@monom.org>
To: Peter Xu <peterx@redhat.com>
Cc: linux-rt-users@vger.kernel.org, John Kacur <jkacur@redhat.com>,
Clark Williams <williams@redhat.com>,
Daniel Wagner <dwagner@suse.de>
Subject: Re: [PATCH] rt-tests: Drop use_current_cpuset() check
Date: Wed, 17 Mar 2021 08:49:03 +0100 [thread overview]
Message-ID: <20210317074903.5lskayjwylnvuhks@beryllium.lan> (raw)
In-Reply-To: <20210316200705.GC395976@xz-x1>
On Tue, Mar 16, 2021 at 04:07:05PM -0400, Peter Xu wrote:
> I think what I'm missing is why we had such a restriction. Quotting from the
> commit ID:
IIRC, the current behavior allows the process to be placed into a cgroup
with a subset of CPUs and you just can do 'cyclictest -a -t'. Process
should not ignore external configuration. That's my whole point here.
> So I'm not sure I understand the word "runtime environment".
>
> If it's defined as "the set of cores that this process is allowed to
> run",
I am trying to say is, the tests should not assume they have the full
control of the placement as this is not what I would expect. If I as
'admin' limits the sched mask then cyclictest should not overwrite it.
If you insist removing this code, please add a section in the
documentation explaining why the tools ignore it.
> John and I had some discussion offlist about this last time on oslat,
As I said, I think this behavior is wrong. Anyway, I stopped caring.
next prev parent reply other threads:[~2021-03-17 7:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 19:37 [PATCH] rt-tests: Drop use_current_cpuset() check Peter Xu
2021-03-16 8:18 ` Daniel Wagner
2021-03-16 20:07 ` Peter Xu
2021-03-17 7:49 ` Daniel Wagner [this message]
2021-03-17 12:51 ` Peter Xu
2021-03-17 15:08 ` John Kacur
2021-03-17 15:21 ` Peter Xu
2021-03-17 15:47 ` John Kacur
2021-03-17 17:20 ` Daniel Wagner
2021-03-17 16:40 ` Ahmed S. Darwish
2021-03-17 17:15 ` Daniel Wagner
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=20210317074903.5lskayjwylnvuhks@beryllium.lan \
--to=wagi@monom.org \
--cc=dwagner@suse.de \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterx@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).