From: subhra mazumdar <subhra.mazumdar@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, mingo@redhat.com,
daniel.lezcano@linaro.org, steven.sistare@oracle.com,
dhaval.giani@oracle.com, rohit.k.jain@oracle.com,
subhra.mazumdar@oracle.com
Subject: [PATCH 2/3] sched: introduce per-cpu var next_cpu to track search limit
Date: Mon, 23 Apr 2018 17:41:15 -0700 [thread overview]
Message-ID: <20180424004116.28151-3-subhra.mazumdar@oracle.com> (raw)
In-Reply-To: <20180424004116.28151-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 5e10aae..cd5c08d 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -17,6 +17,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(HAVE_JUMP_LABEL)
/*
@@ -6018,6 +6019,7 @@ void __init sched_init(void)
struct rq *rq;
rq = cpu_rq(i);
+ per_cpu(next_cpu, i) = -1;
raw_spin_lock_init(&rq->lock);
rq->nr_running = 0;
rq->calc_load_active = 0;
diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
index 3f1874c..a2db041 100644
--- a/kernel/sched/sched.h
+++ b/kernel/sched/sched.h
@@ -902,6 +902,7 @@ extern struct static_key_false sched_smt_present;
#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:[~2018-04-24 0:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 0:41 [RFC/RFT PATCH 0/3] Improve scheduler scalability for fast path subhra mazumdar
2018-04-24 0:41 ` [PATCH 1/3] sched: remove select_idle_core() for scalability subhra mazumdar
2018-04-24 12:46 ` Peter Zijlstra
2018-04-24 21:45 ` Subhra Mazumdar
2018-04-25 17:49 ` Peter Zijlstra
2018-04-30 23:38 ` Subhra Mazumdar
2018-05-01 18:03 ` Peter Zijlstra
2018-05-02 21:58 ` Subhra Mazumdar
2018-05-04 18:51 ` Subhra Mazumdar
2018-05-29 21:36 ` Peter Zijlstra
2018-05-30 22:08 ` Subhra Mazumdar
2018-05-31 9:26 ` Peter Zijlstra
2018-04-24 0:41 ` subhra mazumdar [this message]
2018-04-24 12:47 ` [PATCH 2/3] sched: introduce per-cpu var next_cpu to track search limit Peter Zijlstra
2018-04-24 22:39 ` Subhra Mazumdar
2018-04-24 0:41 ` [PATCH 3/3] sched: limit cpu search and rotate search window for scalability subhra mazumdar
2018-04-24 12:48 ` Peter Zijlstra
2018-04-24 22:43 ` Subhra Mazumdar
2018-04-24 12:48 ` Peter Zijlstra
2018-04-24 22:48 ` Subhra Mazumdar
2018-04-24 12:53 ` Peter Zijlstra
2018-04-25 0:10 ` Subhra Mazumdar
2018-04-25 15:36 ` Peter Zijlstra
2018-04-25 18:01 ` 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=20180424004116.28151-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=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rohit.k.jain@oracle.com \
--cc=steven.sistare@oracle.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