From: Byungchul Park <byungchul.park@lge.com>
To: peterz@infradead.org, mingo@kernel.org, rostedt@goodmis.org
Cc: tglx@linutronix.de, raistlin@linux.it,
linux-kernel@vger.kernel.org, juri.lelli@gmail.com,
bristot@redhat.com, kernel-team@lge.com, joel@joelfernandes.org
Subject: [PATCH v12 0/2] Make find_later_rq() choose a closer cpu in topology
Date: Mon, 4 Jun 2018 17:10:04 +0900 [thread overview]
Message-ID: <1528099806-30632-1-git-send-email-byungchul.park@lge.com> (raw)
Change from v11
-. Rebase onto the latest tip/sched/core
-. make the word 'cpu' in comments be upper case as Ingo did
in the commit 97fb7a0a89
-. Avoid a compile warning caused by mismatching bwt const and
non-const 'struct sched_domain' in find_cpu()
Change from v10
-. modify a comment a bit as Steven suggested
Change from v9
-. modify a comment a bit so to be more clear as Juri suggested
Change from v8
-. add suggested-by Peterz
-. add several comments
Change from v7
-. fix a trivial typo
-. modify commit messages to explain what it does more clearly
-. simplify code with an existing macro
Change from v6
-. add a comment about selection of fallback_cpu incase more than one exist
-. modify a comment explaining what we do wrt PREFER_SIBLING
Change from v5
-. exclude two patches already picked up by peterz
(sched/deadline: Make find_later_rq() choose a closer cpu in topology)
(sched/deadline: Change return value of cpudl_find())
-. apply what peterz fixed for 'prefer sibling', into deadline and rt
Change from v4
-. remove a patch that might cause huge lock contention
(by spin lock(&cpudl.lock) in a hot path of scheduler)
Change from v3
-. rename closest_cpu to best_cpu so that it align with rt
-. protect referring cpudl.elements with cpudl.lock
-. change return value of cpudl_find() to bool
Change from v2
-. add support for SD_PREFER_SIBLING
Change from v1
-. clean up the patch
Byungchul Park (2):
sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq()
sched/rt: Add support for SD_PREFER_SIBLING on find_lowest_rq()
kernel/sched/deadline.c | 82 ++++++++++++++++++++++++++++++++++++++++++++-----
kernel/sched/rt.c | 80 +++++++++++++++++++++++++++++++++++++++++++++--
2 files changed, 152 insertions(+), 10 deletions(-)
--
1.9.1
*** BLURB HERE ***
Byungchul Park (2):
sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq()
sched/rt: Add support for SD_PREFER_SIBLING on find_lowest_rq()
kernel/sched/deadline.c | 80 ++++++++++++++++++++++++++++++++++++++++++++-----
kernel/sched/rt.c | 78 +++++++++++++++++++++++++++++++++++++++++++++--
2 files changed, 148 insertions(+), 10 deletions(-)
--
1.9.1
next reply other threads:[~2018-06-04 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 8:10 Byungchul Park [this message]
2018-06-04 8:10 ` [PATCH v12 1/2] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq() Byungchul Park
2018-06-04 8:10 ` [PATCH v12 2/2] sched/rt: Add support for SD_PREFER_SIBLING on find_lowest_rq() 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=1528099806-30632-1-git-send-email-byungchul.park@lge.com \
--to=byungchul.park@lge.com \
--cc=bristot@redhat.com \
--cc=joel@joelfernandes.org \
--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=raistlin@linux.it \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).