From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: John Kacur <jkacur@redhat.com>
Cc: Sebastian Andrzej Siewior <bigeasy@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: Mon, 16 Jan 2023 19:41:45 +0100 [thread overview]
Message-ID: <Y8WaaXViNE5dEuyc@lx-t490> (raw)
In-Reply-To: <5515f090-51cf-37fd-68a-66283fb0c639@redhat.com>
On Mon, 16 Jan 2023, John Kacur wrote:
>
> On Thu, 12 Jan 2023, Sebastian Andrzej Siewior wrote:
>
> > numa_num_task_cpus() returns here > 100 CPUs while the system has only
> > 32 populated. The BIOS assumes that I can probably use larger CPUs (with
> > more cores) on the socket so the number of "configured CPUs" is rather
> > high.
> > For default configuration, only with the -S option, it makes sense to
> > use the current affinity instead looking at the number of possible CPUs
> > which could be brought online. It still depends on the affinity of the
> > created threads if the additional CPUs can be used. In a container setup
> > this may not be the case.
> >
> > Use sched_getaffinity() to figure out the number of possible CPUs.
...
>
> In cyclictest we have
>
> if (num_threads == -1)
> num_threads = get_available_cpus(affinity_mask);
>
>
> But the num_threads can be set to -1 in OPT_THREADS too,
> not just for OPT_SMP
A sane default for --smp, which is almost-always used in sane cyclictest
invocations, is still valuable IMHO.
Thanks,
--
Ahmed S. Darwish
Linutronix GmbH
next prev parent reply other threads:[~2023-01-16 18:45 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 [this message]
2023-01-16 18:58 ` John Kacur
2023-01-17 8:52 ` Sebastian Andrzej Siewior
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=Y8WaaXViNE5dEuyc@lx-t490 \
--to=darwi@linutronix.de \
--cc=bigeasy@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