From: Byungchul Park <byungchul.park@lge.com>
To: <peterz@infradead.org>, <mingo@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <juri.lelli@gmail.com>,
<rostedt@goodmis.org>, <bristot@redhat.com>,
<kernel-team@lge.com>
Subject: [PATCH v5 3/4] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq()
Date: Tue, 23 May 2017 11:00:58 +0900 [thread overview]
Message-ID: <1495504859-10960-4-git-send-email-byungchul.park@lge.com> (raw)
In-Reply-To: <1495504859-10960-1-git-send-email-byungchul.park@lge.com>
It would be better to avoid pushing tasks to other cpu within
a SD_PREFER_SIBLING domain, instead, get more chances to check other
siblings.
Signed-off-by: Byungchul Park <byungchul.park@lge.com>
---
kernel/sched/deadline.c | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
index 0223694..ada264c 100644
--- a/kernel/sched/deadline.c
+++ b/kernel/sched/deadline.c
@@ -1325,6 +1325,7 @@ static int find_later_rq(struct task_struct *task)
struct cpumask *later_mask = this_cpu_cpumask_var_ptr(local_cpu_mask_dl);
int this_cpu = smp_processor_id();
int cpu = task_cpu(task);
+ int fallback_cpu = -1;
/* Make sure the mask is initialized first */
if (unlikely(!later_mask))
@@ -1385,6 +1386,15 @@ static int find_later_rq(struct task_struct *task)
* already under consideration through later_mask.
*/
if (best_cpu < nr_cpu_ids) {
+ /*
+ * If current domain is SD_PREFER_SIBLING
+ * flaged, we have to get more chances to
+ * check other siblings.
+ */
+ if (sd->flags & SD_PREFER_SIBLING) {
+ fallback_cpu = best_cpu;
+ continue;
+ }
rcu_read_unlock();
return best_cpu;
}
@@ -1393,6 +1403,13 @@ static int find_later_rq(struct task_struct *task)
rcu_read_unlock();
/*
+ * If fallback_cpu is valid, all our guesses failed *except* for
+ * SD_PREFER_SIBLING domain. Now, we can return the fallback cpu.
+ */
+ if (fallback_cpu != -1)
+ return fallback_cpu;
+
+ /*
* At this point, all our guesses failed, we just return
* 'something', and let the caller sort the things out.
*/
--
1.9.1
next prev parent reply other threads:[~2017-05-23 2:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 2:00 [PATCH v5 0/4] Make find_later_rq() choose a closer cpu in topology Byungchul Park
2017-05-23 2:00 ` [PATCH v5 1/4] sched/deadline: " Byungchul Park
2017-07-12 13:13 ` Juri Lelli
2017-07-13 1:38 ` Byungchul Park
2017-08-10 12:08 ` [tip:sched/core] sched/deadline: Make find_later_rq() choose a closer CPU " tip-bot for Byungchul Park
2017-05-23 2:00 ` [PATCH v5 2/4] sched/deadline: Change return value of cpudl_find() Byungchul Park
2017-07-12 13:22 ` Juri Lelli
2017-07-13 1:24 ` Byungchul Park
2017-08-10 12:08 ` [tip:sched/core] " tip-bot for Byungchul Park
2017-05-23 2:00 ` Byungchul Park [this message]
2017-08-03 12:03 ` [PATCH v5 3/4] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq() Peter Zijlstra
2017-08-04 5:16 ` Byungchul Park
2017-05-23 2:00 ` [PATCH v5 4/4] sched/rt: Add support for SD_PREFER_SIBLING on find_lowest_rq() Byungchul Park
2017-06-02 2:19 ` [PATCH v5 0/4] Make find_later_rq() choose a closer cpu in topology Byungchul Park
2017-07-12 2:44 ` Byungchul Park
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=1495504859-10960-4-git-send-email-byungchul.park@lge.com \
--to=byungchul.park@lge.com \
--cc=bristot@redhat.com \
--cc=juri.lelli@gmail.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®