All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH v2] rt-numa: ignore runtime cpumask if -a CPULIST is specified
Date: Fri, 28 Jan 2022 16:08:45 -0500 (EST)	[thread overview]
Message-ID: <97ed969-a641-ae8d-3731-34fab5fab456@redhat.com> (raw)
In-Reply-To: <YfQzN4/oxz9o92Va@linutronix.de>



On Fri, 28 Jan 2022, Sebastian Andrzej Siewior wrote:

> On 2022-01-28 12:44:14 [-0500], John Kacur wrote:
> > I agree that our current method is too restrictive, so I like the basic 
> > idea here.
> > 
> > I think we also need to differentiate between -a with no arguments
> > and -a all. -a with no arguments should inherit the cpumask from the 
> > runtime environment but -a all, should be the same as specifying all the 
> > cpus and ignoring the inherited cpumask.
> 
> do you consider number of online CPUs to not deploy more threads than
> CPUs online in case some were shutdown?

Not sure I understand your question, but what I am saying is that we can 
inherit a cpumask that has less cpus than cpus that are online. So in the 
case of -a, just use the cpus available in the inherited cpumask
in the case of -a all, use all available cpus.

> 
> > Thanks
> > 
> > John
> 
> Sebastian
> 
> 


  reply	other threads:[~2022-01-28 21:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 14:16 [PATCH] rt-numa: optionally ignore runtime cpumask Marcelo Tosatti
2022-01-21 18:16 ` Sebastian Andrzej Siewior
2022-01-24 12:58   ` Marcelo Tosatti
2022-01-24 16:26     ` Sebastian Andrzej Siewior
2022-01-24 16:40       ` Marcelo Tosatti
2022-01-24 16:44         ` Marcelo Tosatti
2022-01-24 17:07         ` Sebastian Andrzej Siewior
2022-01-24 17:50           ` Marcelo Tosatti
2022-01-25 18:40 ` [PATCH] rt-numa: ignore runtime cpumask if -a CPULIST is specified Marcelo Tosatti
2022-01-25 18:46   ` [PATCH v2] " Marcelo Tosatti
2022-01-26  7:21     ` Sebastian Andrzej Siewior
2022-01-28 17:44     ` John Kacur
2022-01-28 18:17       ` Sebastian Andrzej Siewior
2022-01-28 21:08         ` John Kacur [this message]
2022-01-28 18:39       ` [PATCH v3] " Marcelo Tosatti
2022-01-28 21:11         ` 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=97ed969-a641-ae8d-3731-34fab5fab456@redhat.com \
    --to=jkacur@redhat.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.