From: Leonardo Bras <leobras@redhat.com>
To: 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>,
Leonardo Bras <leobras@redhat.com>,
Frederic Weisbecker <frederic@kernel.org>,
Phil Auld <pauld@redhat.com>, Antoine Tenart <atenart@kernel.org>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Wang Yufen <wangyufen@huawei.com>,
mtosatti@redhat.com
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH v2 0/4] CPU isolation improvements
Date: Thu, 13 Oct 2022 15:40:25 -0300 [thread overview]
Message-ID: <20221013184028.129486-1-leobras@redhat.com> (raw)
Patch 1 removes some noise from isolation.c
Patch 2 adds some information about the housekeeping flags and a short
description on what to expect from the HK functions. I would really like
some feedback on this one, since I got all that from the flags usage, and
maybe I am misreading stuff.
In patch 3, I am suggesting making isolcpus have both the _DOMAIN flag and
the _WQ flag, so the _DOMAIN flag is not responsible for isolating cpus on
workqueue operations anymore. This will avoid AND'ing both those bitmaps
every time we need to check for Workqueue isolation, simplifying code and
avoiding cpumask allocation in most cases.
Maybe I am missing something in this move, so please provide feedback.
In patch 4 I use the results from patch 3 and I disallow pcrypt to schedule
work in cpus that are not enabled for workqueue housekeeping, meaning there
will be less work done in those isolated cpus.
Best regards,
Leo
Leonardo Bras (4):
sched/isolation: Fix style issues reported by checkpatch
sched/isolation: Improve documentation
sched/isolation: Add HK_TYPE_WQ to isolcpus=domain
crypto/pcrypt: Do not use isolated CPUs for callback
crypto/pcrypt.c | 9 +++++---
drivers/pci/pci-driver.c | 13 +----------
include/linux/sched/isolation.h | 38 ++++++++++++++++++++-------------
kernel/sched/isolation.c | 4 ++--
kernel/workqueue.c | 1 -
net/core/net-sysfs.c | 1 -
6 files changed, 32 insertions(+), 34 deletions(-)
--
2.38.0
next reply other threads:[~2022-10-13 18:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 18:40 Leonardo Bras [this message]
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
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=20221013184028.129486-1-leobras@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).