public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Ingo Molnar <mingo@redhat.com>, Peter Zijlstra <peterz@infradead.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
	linux-kernel@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>,
	tkjos@google.com, Daniel Lezcano <daniel.lezcano@linaro.org>,
	quentin.perret@linaro.org, chris.redpath@arm.com,
	Dietmar.Eggemann@arm.com
Subject: [RFC][PATCH 0/2] sched: Power optimizations with SCHED_IDLE
Date: Mon, 26 Nov 2018 16:50:22 +0530	[thread overview]
Message-ID: <cover.1543229820.git.viresh.kumar@linaro.org> (raw)

Hello,

The intention behind sending this series is to get some initial feedback
on the idea of specially handling CPUs which only have SCHED_IDLE
activity enqueued on them, before investing too much effort on it. The
current implementation handles very few code-paths and there is a lot
more that we would need to do to make it work well for us.

This allows enqueuing more tasks to a CPUs which only have tasks with
SCHED_IDLE policy currently, as the new tasks should run on them without
any significant delays. And this avoids waking up an otherwise idle CPU,
hence save power without impacting performance.

We don't have lots of SCHED_IDLE tasks in Android currently, but it
should be possible to convert a few of the background tasks and take
advantage of this feature.

Only basic testing is done with the help of rt-app [1] currently to make
sure the task is getting placed correctly.

--
viresh

Viresh Kumar (2):
  sched: Start tracking SCHED_IDLE tasks count in cfs_rq
  sched: Enqueue tasks on a cpu with only SCHED_IDLE tasks

 kernel/sched/core.c  | 23 ++++++++++++++++
 kernel/sched/fair.c  | 64 +++++++++++++++++++++++++++++++++-----------
 kernel/sched/sched.h |  5 ++++
 3 files changed, 76 insertions(+), 16 deletions(-)

-- 
2.19.1.568.g152ad8e3369a

[1] json: https://pastebin.ubuntu.com/p/Y4fr9xddV8/


             reply	other threads:[~2018-11-26 11:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 11:20 Viresh Kumar [this message]
2018-11-26 11:20 ` [RFC][PATCH 1/2] sched: Start tracking SCHED_IDLE tasks count in cfs_rq Viresh Kumar
2018-11-26 11:20 ` [RFC][PATCH 2/2] sched: Enqueue tasks on a cpu with only SCHED_IDLE tasks Viresh Kumar
2018-11-26 12:37   ` Quentin Perret
2018-11-27 10:24     ` Viresh Kumar
2018-11-27 11:00       ` Quentin Perret

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=cover.1543229820.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --cc=Dietmar.Eggemann@arm.com \
    --cc=chris.redpath@arm.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=quentin.perret@linaro.org \
    --cc=tkjos@google.com \
    --cc=vincent.guittot@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