From: <byungchul.park@lge.com>
To: mingo@kernel.org, peterz@infradead.org
Cc: linux-kernel@vger.kernel.org, yuyang.du@intel.com,
pjt@google.com, efault@gmx.de, tglx@linutronix.de,
Byungchul Park <byungchul.park@lge.com>
Subject: [PATCH v3 0/3] sched: account fair load avg consistently
Date: Thu, 15 Oct 2015 18:01:13 +0900 [thread overview]
Message-ID: <1444899676-5852-1-git-send-email-byungchul.park@lge.com> (raw)
From: Byungchul Park <byungchul.park@lge.com>
* change from v2 to v3
- consider otimization in the case of migration
- split patches to 3 to be reviewed easily
* change from v1 to v2
- make set_task_rq() do that role instead of migration callback
- make set_task_rq() do that role instead of move group callback
- remove the dependancy between last_update_time and check for migration
Byungchul Park (3):
sched: introduce a new migration flag to task_struct
sched: factor out the code getting cfs_rq's last_update_time
sched: make it possible to account fair class load avg consistently
include/linux/sched.h | 3 +++
kernel/sched/core.c | 1 +
kernel/sched/fair.c | 63 ++++++++++++++++++++++++++++++++-----------------
kernel/sched/sched.h | 5 ++++
4 files changed, 51 insertions(+), 21 deletions(-)
--
1.7.9.5
next reply other threads:[~2015-10-15 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 9:01 byungchul.park [this message]
2015-10-15 9:01 ` [PATCH v3 1/3] sched: introduce a new migration flag to task_struct byungchul.park
2015-10-15 11:18 ` Peter Zijlstra
2015-10-15 12:26 ` Byungchul Park
2015-10-15 18:34 ` Peter Zijlstra
2015-10-15 9:01 ` [PATCH v3 2/3] sched: factor out the code getting cfs_rq's last_update_time byungchul.park
2015-10-15 9:01 ` [PATCH v3 3/3] sched: make it possible to account fair class load avg consistently 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=1444899676-5852-1-git-send-email-byungchul.park@lge.com \
--to=byungchul.park@lge.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=tglx@linutronix.de \
--cc=yuyang.du@intel.com \
/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®