From: "Leonardo Brás" <leobras@redhat.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Bjorn Helgaas <bhelgaas@google.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Phil Auld <pauld@redhat.com>, Antoine Tenart <atenart@kernel.org>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Wang Yufen <wangyufen@huawei.com>,
mtosatti@redhat.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 2/4] sched/isolation: Improve documentation
Date: Sat, 17 Dec 2022 02:04:03 -0300 [thread overview]
Message-ID: <5bf73d21c03d4a642eb81de35544a4d6cfa9294c.camel@redhat.com> (raw)
In-Reply-To: <20221129115439.GA1715045@lothringen>
On Tue, 2022-11-29 at 12:54 +0100, Frederic Weisbecker wrote:
> On Thu, Oct 13, 2022 at 03:40:27PM -0300, Leonardo Bras wrote:
> > Improve documentation on housekeeping types and what to expect from
> > housekeeping functions.
> >
> > Signed-off-by: Leonardo Bras <leobras@redhat.com>
> > ---
> > include/linux/sched/isolation.h | 25 ++++++++++++++++---------
> > 1 file changed, 16 insertions(+), 9 deletions(-)
> >
> > diff --git a/include/linux/sched/isolation.h b/include/linux/sched/isolation.h
> > index 762701f295d1c..9333c28153a7a 100644
> > --- a/include/linux/sched/isolation.h
> > +++ b/include/linux/sched/isolation.h
> > @@ -7,18 +7,25 @@
> > #include <linux/tick.h>
> >
> > enum hk_type {
> > - HK_TYPE_TIMER,
> > - HK_TYPE_RCU,
> > - HK_TYPE_MISC,
> > - HK_TYPE_SCHED,
> > - HK_TYPE_TICK,
> > - HK_TYPE_DOMAIN,
> > - HK_TYPE_WQ,
> > - HK_TYPE_MANAGED_IRQ,
> > - HK_TYPE_KTHREAD,
> > + HK_TYPE_TIMER, /* Timer interrupt, watchdogs */
>
> More precisely:
>
> /* Unbound timer callbacks */
>
> > + HK_TYPE_RCU, /* RCU callbacks */
>
> More generally, because it's more than just about callbacks:
>
> /* Unbound RCU work */
Both updated, thanks!
Out of curiosity, what does 'Unbound' means in this context?
>
> > + HK_TYPE_MISC, /* Minor housekeeping categories */
> > + HK_TYPE_SCHED, /* Scheduling and idle load balancing */
> > + HK_TYPE_TICK, /* See isolcpus=nohz boot parameter */
>
> Yes or nohz_full=
>
> > + HK_TYPE_DOMAIN, /* See isolcpus=domain boot parameter*/
> > + HK_TYPE_WQ, /* Work Queues*/
>
> /* Unbound workqueues */
>
> > + HK_TYPE_MANAGED_IRQ, /* See isolcpus=managed_irq boot parameter */
> > + HK_TYPE_KTHREAD, /* kernel threads */
>
> /* Unbound kernel threads */
>
>
> > HK_TYPE_MAX
> > };
> >
> > +/* Kernel parameters like nohz_full and isolcpus allow passing cpu numbers
> > + * for disabling housekeeping types.
> > + *
> > + * The functions bellow work the opposite way, by referencing which cpus
> > + * are able to perform the housekeeping type in parameter.
> > + */
>
> *below
>
> Thanks!
Done, done, done, done.
Thanks a lot for reviewing!
Best regards,
Leo
>
> > +
> > #ifdef CONFIG_CPU_ISOLATION
> > DECLARE_STATIC_KEY_FALSE(housekeeping_overridden);
> > int housekeeping_any_cpu(enum hk_type type);
> > --
> > 2.38.0
> >
>
next prev parent reply other threads:[~2022-12-17 5:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 18:40 [PATCH v2 0/4] CPU isolation improvements Leonardo Bras
2022-10-13 18:40 ` [PATCH v2 1/4] sched/isolation: Fix style issues reported by checkpatch Leonardo Bras
2022-10-14 8:28 ` Peter Zijlstra
2022-10-13 18:40 ` [PATCH v2 2/4] sched/isolation: Improve documentation Leonardo Bras
2022-10-14 8:32 ` Peter Zijlstra
2022-10-14 15:40 ` Leonardo Bras Soares Passos
2022-11-29 11:54 ` Frederic Weisbecker
2022-12-17 5:04 ` Leonardo Brás [this message]
2022-10-13 18:40 ` [PATCH v2 3/4] sched/isolation: Add HK_TYPE_WQ to isolcpus=domain Leonardo Bras
2022-10-14 8:36 ` Peter Zijlstra
2022-10-14 13:24 ` Frederic Weisbecker
2022-10-14 16:27 ` Leonardo Brás
2022-11-29 12:10 ` Frederic Weisbecker
2022-12-20 6:57 ` Leonardo Brás
2022-10-13 18:40 ` [PATCH v2 4/4] crypto/pcrypt: Do not use isolated CPUs for callback Leonardo Bras
2023-05-27 0:47 ` Leonardo Bras Soares Passos
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=5bf73d21c03d4a642eb81de35544a4d6cfa9294c.camel@redhat.com \
--to=leobras@redhat.com \
--cc=atenart@kernel.org \
--cc=bhelgaas@google.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=dietmar.eggemann@arm.com \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jiangshanlai@gmail.com \
--cc=juri.lelli@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=steffen.klassert@secunet.com \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=wangyufen@huawei.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).