From: Rohit Jain <rohit.k.jain@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, mingo@redhat.com
Subject: [PATCH 0/2] Interrupt Aware Scheduler
Date: Fri, 12 May 2017 11:04:25 -0700 [thread overview]
Message-ID: <1494612267-29465-1-git-send-email-rohit.k.jain@oracle.com> (raw)
This patch introduces Interrupt Aware Scheduler(IAS). The tests till now
show an overall improvement in cases where the workload has some
interrupt activity.
The patch avoids CPUs which might be considered interrupt-heavy when
trying to schedule threads (on the push side) in the system. Interrupt
Awareness has only been added into the fair scheduling class.
Rohit Jain (2):
sched: Interrupt Aware Scheduler
tools/testing: Adding tests to showcase the efficacy of IAS
kernel/sched/core.c | 42 +++++++++++++++++++
kernel/sched/cputime.c | 6 ++-
kernel/sched/fair.c | 52 ++++++++++++++++++------
kernel/sched/loadavg.c | 40 ++++++++++++++++++
kernel/sched/sched.h | 37 ++++++++++++++++-
tools/testing/selftests/openmp_barrier/Makefile | 6 +++
tools/testing/selftests/openmp_barrier/barrier.c | 29 +++++++++++++
7 files changed, 197 insertions(+), 15 deletions(-)
create mode 100644 tools/testing/selftests/openmp_barrier/Makefile
create mode 100644 tools/testing/selftests/openmp_barrier/barrier.c
--
2.7.4
next reply other threads:[~2017-05-12 18:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 18:04 Rohit Jain [this message]
2017-05-12 18:04 ` [PATCH 1/2] sched: Interrupt Aware Scheduler Rohit Jain
2017-05-12 19:46 ` Peter Zijlstra
2017-05-12 20:19 ` Rohit Jain
2017-05-17 7:52 ` Vincent Guittot
2017-05-18 17:24 ` Rohit Jain
2017-05-12 18:04 ` [PATCH 2/2] tools/testing: Adding tests to showcase the efficacy of IAS Rohit Jain
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=1494612267-29465-1-git-send-email-rohit.k.jain@oracle.com \
--to=rohit.k.jain@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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).