From: Yury Norov <yury.norov@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: 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>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v2 0/2] bitmap_parselist: support 'all' semantics
Date: Wed, 21 Apr 2021 10:49:50 -0700 [thread overview]
Message-ID: <20210421174950.GA106553@yury-ThinkPad> (raw)
In-Reply-To: <20210421173008.GV975577@paulmck-ThinkPad-P17-Gen-1>
On Wed, Apr 21, 2021 at 10:30:08AM -0700, Paul E. McKenney wrote:
> On Tue, Apr 20, 2021 at 08:13:24PM -0700, Yury Norov wrote:
> > RCU code supports a special group 'all' which selects all bits in a bitmap.
> > We have recently added 'N' extension for bitmap parse, so that '0-N' would
> > have exactly the same meaning as 'all'. But because the 'all' is already
> > used by RCU, it would be reasonable to support it in core bitmap code as a
> > common and easy-readable alias for '0-N'.
> >
> > Moving the 'all' support to core bitmap code adds another level of
> > flexibility for system configuration by supporting patterns. For example,
> > every second bit in cpumask may be selected like this:
> > isolcpus=all:1/2
> >
> > v2:
> > - cleanup patch 1;
> > - in patch 2 explain why dropping legacy comment.
>
> Nice!
>
> I have pulled this into -rcu with some minor updates, including replacing
> the "isolcpus=all" with "rcu_nocbs=all:1/2" per Steve Rostedt's feedback.
Thank you Paul and Steven for fixing this 'isolcpus=all'.
'rcu_nocbs=all:1/2' would look better in the documentation.
> Could you please check to make sure that I didn't mess anything up?
Everything is OK. Thank you for fixing this.
> If tests go well, this will go into -next later today or tomorrow.
> Although I cannot prove that this will not make the upcoming merge window,
> but Murphy insists that it will instead be the v5.14 merge window.
>
> Thanx, Paul
>
> > Yury Norov (2):
> > bitmap_parse: support 'all' semantics
> > rcu/tree_plugin: don't handle the case of 'all' CPU range
> >
> > Documentation/admin-guide/kernel-parameters.rst | 5 +++++
> > kernel/rcu/tree_plugin.h | 9 +++------
> > lib/bitmap.c | 9 +++++++++
> > lib/test_bitmap.c | 7 +++++++
> > 4 files changed, 24 insertions(+), 6 deletions(-)
> >
> > --
> > 2.25.1
> >
prev parent reply other threads:[~2021-04-21 17:49 UTC|newest]
Thread overview: 8+ 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
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 [this message]
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=20210421174950.GA106553@yury-ThinkPad \
--to=yury.norov@gmail.com \
--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=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
/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).