From: Waiman Long <longman@redhat.com>
To: 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>,
Valentin Schneider <vschneid@redhat.com>,
Frederic Weisbecker <frederic@kernel.org>
Cc: linux-kernel@vger.kernel.org, Phil Auld <pauld@redhat.com>,
Waiman Long <longman@redhat.com>
Subject: [PATCH v3 0/2] sched: Miscellaneous isolation related cleanups
Date: Wed, 4 Sep 2024 14:36:48 -0400 [thread overview]
Message-ID: <20240904183650.1053708-1-longman@redhat.com> (raw)
v3:
- Fix incorrect housekeeping_nohz_full_setup() flags setting.
v2:
- Remove HK_TYPE_SCHED and related dead code
- Change consolidated name from HK_TYPE_NOHZ_FULL to
HK_TYPE_KERNEL_NOSISE as suggested by Frederic and update
isolation.c as well.
This series contains a number of miscellaneous sched/isolation related
cleanups.
[v1] https://lore.kernel.org/lkml/20240818234520.90186-1-longman@redhat.com/
[v2] https://lore.kernel.org/lkml/20240904171441.1048072-1-longman@redhat.com/
Waiman Long (2):
sched/core: Remove HK_TYPE_SCHED
sched/isolation: Consolidate housekeeping cpumasks that are always
identical
include/linux/sched/isolation.h | 19 ++++++++++++-------
kernel/sched/fair.c | 14 --------------
kernel/sched/isolation.c | 10 ++--------
3 files changed, 14 insertions(+), 29 deletions(-)
--
2.43.5
next reply other threads:[~2024-09-04 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 18:36 Waiman Long [this message]
2024-09-04 18:36 ` [PATCH v3 1/2] sched/core: Remove HK_TYPE_SCHED Waiman Long
2024-09-04 18:36 ` [PATCH v3 2/2] sched/isolation: Consolidate housekeeping cpumasks that are always identical Waiman Long
2024-09-04 21:18 ` Frederic Weisbecker
2024-09-04 23:57 ` Waiman Long
2024-09-06 13:10 ` Frederic Weisbecker
2024-09-07 1:06 ` Waiman Long
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=20240904183650.1053708-1-longman@redhat.com \
--to=longman@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®