From: "Paul E. McKenney" <paulmck@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Yury Norov <yury.norov@gmail.com>,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
linux-doc@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Joel Fernandes <joel@joelfernandes.org>,
Jonathan Corbet <corbet@lwn.net>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Randy Dunlap <rdunlap@infradead.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH 1/2] bitmap_parse: support 'all' semantics
Date: Wed, 21 Apr 2021 08:57:48 -0700 [thread overview]
Message-ID: <20210421155748.GU975577@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20210421111932.36665920@gandalf.local.home>
On Wed, Apr 21, 2021 at 11:19:32AM -0400, Steven Rostedt wrote:
> On Tue, 20 Apr 2021 20:13:25 -0700
> Yury Norov <yury.norov@gmail.com> wrote:
>
> > @@ -76,6 +76,11 @@ to change, such as less cores in the CPU list, then N and any ranges using N
> > will also change. Use the same on a small 4 core system, and "16-N" becomes
> > "16-3" and now the same boot input will be flagged as invalid (start > end).
> >
> > +The special case-tolerant group name "all" has a meaning of selecting all CPUs,
> > +such that "isolcpus=all" is the equivalent of "isolcpus=0-N".
>
> I'm OK with the concept of this patch set, but really? That is a horrible
> example. One should NEVER set isolcpus to all!
How about "isolcpus=all:2/4"? ;-)
Thanx, Paul
> -- Steve
>
>
> > +
> > +The semantics of "N" and "all" is supported on a level of bitmaps and holds for
> > +all users of bitmap_parse().
> >
next prev parent reply other threads:[~2021-04-21 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 3:13 [PATCH v2 0/2] bitmap_parselist: support 'all' semantics Yury Norov
2021-04-21 3:13 ` [PATCH 1/2] bitmap_parse: " Yury Norov
2021-04-21 15:19 ` Steven Rostedt
2021-04-21 15:57 ` Paul E. McKenney [this message]
2021-04-21 23:45 ` Paul Gortmaker
2021-04-21 3:13 ` [PATCH 2/2] rcu/tree_plugin: don't handle the case of 'all' CPU range Yury Norov
2021-04-21 17:30 ` [PATCH v2 0/2] bitmap_parselist: support 'all' semantics Paul E. McKenney
2021-04-21 17:49 ` Yury Norov
-- strict thread matches above, loose matches on Subject: below --
2021-04-20 0:01 [PATCH " Yury Norov
2021-04-20 0:01 ` [PATCH 1/2] bitmap_parse: " Yury Norov
2021-04-20 10:17 ` Andy Shevchenko
2021-04-20 19:32 ` Yury Norov
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=20210421155748.GU975577@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mathieu.desnoyers@efficios.com \
--cc=palmerdabbelt@google.com \
--cc=paul.gortmaker@windriver.com \
--cc=rcu@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=yury.norov@gmail.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).