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>,
	linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>
Subject: [PATCH 0/6] sched: Minor fixes and cleanups
Date: Wed, 24 May 2017 10:59:51 +0530	[thread overview]
Message-ID: <cover.1495603536.git.viresh.kumar@linaro.org> (raw)

Hi,

The first patch fixes a potential regression we may observe on the UP
systems and the others are doing minor optimizations in the scheduler
core.

They are all tested on ARM 32 (exynos) and 64 (hikey) bit platforms.

--
viresh

Viresh Kumar (6):
  sched: fair: Call cpufreq update util handlers less frequently on UP
  sched: Reuse put_prev_task()
  sched: fair: Pass rq to weighted_cpuload()
  sched: fair: Avoid checking cfs_rq->nr_running twice
  sched: fair: Drop always true parameter of update_cfs_rq_load_avg()
  sched: cpufreq: Optimize cpufreq_update_this_cpu() a bit

 kernel/sched/core.c  |   2 +-
 kernel/sched/fair.c  | 107 ++++++++++++++++++++++++++-------------------------
 kernel/sched/sched.h |   2 +-
 3 files changed, 56 insertions(+), 55 deletions(-)

-- 
2.13.0.70.g6367777092d9

             reply	other threads:[~2017-05-24  5:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24  5:29 Viresh Kumar [this message]
2017-05-24  5:29 ` [PATCH 1/6] sched: fair: Call cpufreq update util handlers less frequently on UP Viresh Kumar
2017-08-10 12:03   ` [tip:sched/core] sched/fair: " tip-bot for Viresh Kumar
2017-05-24  5:29 ` [PATCH 2/6] sched: Reuse put_prev_task() Viresh Kumar
2017-08-10 12:04   ` [tip:sched/core] sched/core: " tip-bot for Viresh Kumar
2017-05-24  5:29 ` [PATCH 3/6] sched: fair: Pass rq to weighted_cpuload() Viresh Kumar
2017-08-10 12:04   ` [tip:sched/core] sched/fair: Pass 'rq' " tip-bot for Viresh Kumar
2017-05-24  5:29 ` [PATCH 4/6] sched: fair: Avoid checking cfs_rq->nr_running twice Viresh Kumar
2017-08-10 12:04   ` [tip:sched/core] sched/fair: " tip-bot for Viresh Kumar
2017-05-24  5:29 ` [PATCH 5/6] sched: fair: Drop always true parameter of update_cfs_rq_load_avg() Viresh Kumar
2017-08-10 12:05   ` [tip:sched/core] sched/fair: " tip-bot for Viresh Kumar
2017-05-24  5:29 ` [PATCH 6/6] sched: cpufreq: Optimize cpufreq_update_this_cpu() a bit Viresh Kumar
2017-06-27  4:24 ` [PATCH 0/6] sched: Minor fixes and cleanups Viresh Kumar

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.1495603536.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --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