From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: John Kacur <jkacur@redhat.com>
Cc: "Ahmed S. Darwish" <darwi@linutronix.de>,
Clark Williams <williams@redhat.com>,
linux-rt-users@vger.kernel.org
Subject: Re: [PATCH] rt-numa: Use a reasonable default max CPU value.
Date: Tue, 17 Jan 2023 09:52:46 +0100 [thread overview]
Message-ID: <Y8Zh3h17Fu1uChsa@linutronix.de> (raw)
In-Reply-To: <25a775d-77e-e76e-a626-1e6c605e1df3@redhat.com>
On 2023-01-16 13:58:42 [-0500], John Kacur wrote:
>
> Okay, not sure how that adds to the conversation. I'm all for "sane"
> defaults for --smp too, but we care about other kinds of invocations too.
> As soon as I get a patch that doesn't break other things as well, I'll
> apply it.
BROKEN IT IS.
I want to use that and not fix every time I use it. Using
-S -p 90 -d0 -m
are already a lot of options just for a simple test to use all CPUs on a
system. This used to work on this machine. Now it starts way more
threads than I have CPUs. I accept that this might be something that
someone wants to test so he can use -t 100. But the simple test that is
no longer working. srsly. Starting more threads than the current
available online CPUs or even CPU affinity makes no sense since the
results with equal priority distribution or not reproducible.
> John
Sebastian
next prev parent reply other threads:[~2023-01-17 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 10:00 [PATCH] rt-numa: Use a reasonable default max CPU value Sebastian Andrzej Siewior
2023-01-16 18:15 ` John Kacur
2023-01-16 18:41 ` Ahmed S. Darwish
2023-01-16 18:58 ` John Kacur
2023-01-17 8:52 ` Sebastian Andrzej Siewior [this message]
2023-01-17 22:50 ` John Kacur
-- strict thread matches above, loose matches on Subject: below --
2023-01-19 19:51 John Kacur
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=Y8Zh3h17Fu1uChsa@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=darwi@linutronix.de \
--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