From: subhra mazumdar <subhra.mazumdar@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, mingo@redhat.com, tglx@linutronix.de,
steven.sistare@oracle.com, dhaval.giani@oracle.com,
daniel.lezcano@linaro.org, vincent.guittot@linaro.org,
viresh.kumar@linaro.org, tim.c.chen@linux.intel.com,
mgorman@techsingularity.net
Subject: [PATCH v3 2/7] sched: introduce per-cpu var next_cpu to track search limit
Date: Wed, 26 Jun 2019 18:29:14 -0700 [thread overview]
Message-ID: <20190627012919.4341-3-subhra.mazumdar@oracle.com> (raw)
In-Reply-To: <20190627012919.4341-1-subhra.mazumdar@oracle.com>
Introduce a per-cpu variable to track the limit upto which idle cpu search
was done in select_idle_cpu(). This will help to start the search next time
from there. This is necessary for rotating the search window over entire
LLC domain.
Signed-off-by: subhra mazumdar <subhra.mazumdar@oracle.com>
---
kernel/sched/core.c | 2 ++
kernel/sched/sched.h | 1 +
2 files changed, 3 insertions(+)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 874c427..80657fc 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -24,6 +24,7 @@
#include <trace/events/sched.h>
DEFINE_PER_CPU_SHARED_ALIGNED(struct rq, runqueues);
+DEFINE_PER_CPU_SHARED_ALIGNED(int, next_cpu);
#if defined(CONFIG_SCHED_DEBUG) && defined(CONFIG_JUMP_LABEL)
/*
@@ -5966,6 +5967,7 @@ void __init sched_init(void)
for_each_possible_cpu(i) {
struct rq *rq;
+ per_cpu(next_cpu, i) = -1;
rq = cpu_rq(i);
raw_spin_lock_init(&rq->lock);
rq->nr_running = 0;
diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
index b52ed1a..4cecfa2 100644
--- a/kernel/sched/sched.h
+++ b/kernel/sched/sched.h
@@ -994,6 +994,7 @@ static inline void update_idle_core(struct rq *rq) { }
#endif
DECLARE_PER_CPU_SHARED_ALIGNED(struct rq, runqueues);
+DECLARE_PER_CPU_SHARED_ALIGNED(int, next_cpu);
#define cpu_rq(cpu) (&per_cpu(runqueues, (cpu)))
#define this_rq() this_cpu_ptr(&runqueues)
--
2.9.3
next prev parent reply other threads:[~2019-06-27 1:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 1:29 [RESEND PATCH v3 0/7] Improve scheduler scalability for fast path subhra mazumdar
2019-06-27 1:29 ` [PATCH v3 1/7] sched: limit cpu search in select_idle_cpu subhra mazumdar
2019-06-28 18:47 ` Parth Shah
2019-06-28 22:21 ` Subhra Mazumdar
2019-06-27 1:29 ` subhra mazumdar [this message]
2019-06-27 1:29 ` [PATCH v3 3/7] sched: rotate the cpu search window for better spread subhra mazumdar
2019-06-28 11:54 ` Srikar Dronamraju
2019-06-28 22:34 ` Subhra Mazumdar
2019-06-28 18:36 ` Parth Shah
2019-06-28 22:14 ` Subhra Mazumdar
2019-06-27 1:29 ` [PATCH v3 4/7] sched: add sched feature to disable idle core search subhra mazumdar
2019-06-27 1:29 ` [PATCH v3 5/7] sched: SIS_CORE " subhra mazumdar
2019-06-28 19:01 ` Parth Shah
2019-06-28 22:29 ` Subhra Mazumdar
2019-07-01 9:57 ` Parth Shah
2019-07-01 20:37 ` Subhra Mazumdar
2019-07-04 12:34 ` Parth Shah
2019-07-14 1:16 ` Subhra Mazumdar
2019-06-27 1:29 ` [PATCH v3 6/7] x86/smpboot: introduce per-cpu variable for HT siblings subhra mazumdar
2019-06-27 6:51 ` Thomas Gleixner
2019-06-27 6:54 ` Thomas Gleixner
2019-06-28 1:06 ` Subhra Mazumdar
2019-06-28 1:02 ` Subhra Mazumdar
2019-06-27 1:29 ` [PATCH v3 7/7] sched: use per-cpu variable cpumask_weight_sibling subhra mazumdar
2019-07-01 9:02 ` [RESEND PATCH v3 0/7] Improve scheduler scalability for fast path Peter Zijlstra
2019-07-01 13:55 ` Patrick Bellasi
2019-07-01 14:04 ` Peter Zijlstra
2019-07-08 22:32 ` Tim Chen
2019-07-01 14:06 ` Peter Zijlstra
2019-07-02 0:01 ` Subhra Mazumdar
2019-07-02 8:54 ` Patrick Bellasi
2019-07-03 3:52 ` Subhra Mazumdar
2019-07-04 11:35 ` Parth Shah
-- strict thread matches above, loose matches on Subject: below --
2019-06-09 1:49 [PATCH " subhra mazumdar
2019-06-09 1:49 ` [PATCH v3 2/7] sched: introduce per-cpu var next_cpu to track search limit subhra mazumdar
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=20190627012919.4341-3-subhra.mazumdar@oracle.com \
--to=subhra.mazumdar@oracle.com \
--cc=daniel.lezcano@linaro.org \
--cc=dhaval.giani@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=steven.sistare@oracle.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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).