From: Valentin Schneider <valentin.schneider@arm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, peterz@infradead.org, mgorman@suse.de,
riel@surriel.com
Subject: [PATCH 0/3] sched/fair: Init NUMA task_work in sched_fork()
Date: Mon, 15 Jul 2019 11:25:05 +0100 [thread overview]
Message-ID: <20190715102508.32434-1-valentin.schneider@arm.com> (raw)
A TODO has been sitting in task_tick_numa() regarding init'ing the
task_numa_work() task_work in sched_fork() rather than in task_tick_numa(),
so I figured I'd have a go at it.
Patches 1 & 2 do that, and patch 3 is a freebie cleanup.
Briefly tested on a 2 * (Xeon E5-2690) system, didn't see any obvious
breakage.
Valentin Schneider (3):
sched/fair: Move init_numa_balancing() below task_numa_work()
sched/fair: Move task_numa_work() init to init_numa_balancing()
sched/fair: Change task_numa_work() storage to static
kernel/sched/fair.c | 93 +++++++++++++++++++++++----------------------
1 file changed, 47 insertions(+), 46 deletions(-)
--
2.22.0
next reply other threads:[~2019-07-15 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 10:25 Valentin Schneider [this message]
2019-07-15 10:25 ` [PATCH 1/3] sched/fair: Move init_numa_balancing() below task_numa_work() Valentin Schneider
2019-07-25 16:11 ` [tip:sched/core] " tip-bot for Valentin Schneider
2019-07-15 10:25 ` [PATCH 2/3] sched/fair: Move task_numa_work() init to init_numa_balancing() Valentin Schneider
2019-07-25 16:12 ` [tip:sched/core] " tip-bot for Valentin Schneider
2019-07-15 10:25 ` [PATCH 3/3] sched/fair: Change task_numa_work() storage to static Valentin Schneider
2019-07-25 16:13 ` [tip:sched/core] " tip-bot for Valentin Schneider
2019-07-15 10:48 ` [PATCH 0/3] sched/fair: Init NUMA task_work in sched_fork() Peter Zijlstra
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=20190715102508.32434-1-valentin.schneider@arm.com \
--to=valentin.schneider@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.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).