From: Yuyang Du <yuyang.du@intel.com>
To: mingo@kernel.org, peterz@infradead.org, linux-kernel@vger.kernel.org
Cc: pjt@google.com, bsegall@google.com, morten.rasmussen@arm.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
matt@codeblueprint.co.uk, umgwanakikbuti@gmail.com,
Yuyang Du <yuyang.du@intel.com>
Subject: [RESEND PATCH 0/2] sched/fair: Add documentation and optimize __update_sched_avg()
Date: Mon, 13 Feb 2017 05:44:21 +0800 [thread overview]
Message-ID: <1486935863-25251-1-git-send-email-yuyang.du@intel.com> (raw)
Hi Peter,
I found I have some patches that go nowhere, out of which two stand out. So I resend them.
The first one adds a document about how to calculate the constants used in load tracking,
which was suggested by you and mentioned in commit 7b20b916e953cabef569541f991a0a583bc344cb
Author: Yuyang Du <yuyang.du@intel.com>
Date: Tue May 3 05:54:27 2016 +0800
sched/fair: Optimize sum computation with a lookup table
And the second one attempts to optimize __update_sched_avg(), mostly resulting in code simplification.
These two patches have NO changes made to the names nor functions in the existing codes.
Would you please give it a look?
Thanks,
Yuyang
--
Yuyang Du (2):
documentation: Add scheduler/sched-avg.txt
sched/fair: Optimize __update_sched_avg()
Documentation/scheduler/sched-avg.txt | 94 ++++++++++++++++++
kernel/sched/fair.c | 174 +++++++++++++++++-----------------
2 files changed, 182 insertions(+), 86 deletions(-)
create mode 100644 Documentation/scheduler/sched-avg.txt
--
2.1.4
next reply other threads:[~2017-02-13 5:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 21:44 Yuyang Du [this message]
2017-02-12 21:44 ` [RESEND PATCH 1/2] documentation: Add scheduler/sched-avg.txt Yuyang Du
2017-04-14 9:28 ` [tip:sched/core] sched/Documentation: Add 'sched-pelt' tool tip-bot for Yuyang Du
2017-02-12 21:44 ` [RESEND PATCH 2/2] sched/fair: Optimize __update_sched_avg() Yuyang Du
2017-03-28 12:50 ` Peter Zijlstra
2017-03-28 23:57 ` Yuyang Du
2017-03-28 14:46 ` Peter Zijlstra
2017-03-29 0:04 ` Yuyang Du
2017-03-29 10:41 ` Peter Zijlstra
2017-03-29 18:41 ` Yuyang Du
2017-03-30 11:21 ` Paul Turner
2017-03-30 12:16 ` Peter Zijlstra
2017-03-30 13:46 ` Peter Zijlstra
2017-03-30 18:50 ` Yuyang Du
2017-03-30 14:14 ` Peter Zijlstra
2017-03-30 19:13 ` Yuyang Du
2017-03-30 19:41 ` Yuyang Du
2017-03-31 7:13 ` Peter Zijlstra
2017-03-30 22:02 ` Paul Turner
2017-03-31 7:01 ` Peter Zijlstra
2017-03-31 9:58 ` Paul Turner
2017-03-31 11:23 ` Peter Zijlstra
2017-04-10 7:39 ` Dietmar Eggemann
2017-04-10 8:40 ` Peter Zijlstra
2017-03-31 11:30 ` Peter Zijlstra
2017-03-31 10:55 ` Paul Turner
2017-03-31 11:38 ` Peter Zijlstra
2017-04-10 10:47 ` Peter Zijlstra
2017-03-30 18:39 ` Yuyang Du
2017-03-30 8:32 ` [tip:sched/core] sched/fair: Optimize ___update_sched_avg() tip-bot for Yuyang Du
2017-02-28 0:59 ` [RESEND PATCH 0/2] sched/fair: Add documentation and optimize __update_sched_avg() Yuyang Du
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=1486935863-25251-1-git-send-email-yuyang.du@intel.com \
--to=yuyang.du@intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=umgwanakikbuti@gmail.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
all inboxes | Powered by JetHome®