From: Yuyang Du <yuyang.du@intel.com>
To: peterz@infradead.org, mingo@kernel.org, linux-kernel@vger.kernel.org
Cc: bsegall@google.com, pjt@google.com, morten.rasmussen@arm.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
juri.lelli@arm.com, Yuyang Du <yuyang.du@intel.com>
Subject: [PATCH 4/6] sched/fair: Add __always_inline compiler attribute to __accumulate_sum()
Date: Thu, 28 Apr 2016 10:56:11 +0800 [thread overview]
Message-ID: <1461812173-32439-5-git-send-email-yuyang.du@intel.com> (raw)
In-Reply-To: <1461812173-32439-1-git-send-email-yuyang.du@intel.com>
Everybody has it. If code-size is not the problem, __accumulate_sum()
should have it too.
Signed-off-by: Yuyang Du <yuyang.du@intel.com>
---
kernel/sched/fair.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index abfe17a..486f098 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -2649,7 +2649,7 @@ static __always_inline u64 __decay_sum(u64 val, u32 n)
* We can compute this efficiently by combining:
* y^32 = 1/2 with precomputed \Sum 1024*y^n (where n < 32)
*/
-static u32 __accumulate_sum(u32 n)
+static __always_inline u32 __accumulate_sum(u32 n)
{
u32 contrib = 0;
--
1.7.9.5
next prev parent reply other threads:[~2016-04-28 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 2:56 [PATCH 0/6] Optimize sched averages computation Yuyang Du
2016-04-28 2:56 ` [PATCH 1/6] sched/fair: Optimize sum computation with a lookup table Yuyang Du
2016-04-28 17:26 ` bsegall
2016-04-28 2:56 ` [PATCH 2/6] sched/fair: Rename variable names for sched averages Yuyang Du
2016-04-28 2:56 ` [PATCH 3/6] sched/fair: Change the variable to hold the number of periods to 32bit integer Yuyang Du
2016-04-28 17:29 ` bsegall
2016-04-28 18:33 ` Yuyang Du
2016-04-28 2:56 ` Yuyang Du [this message]
2016-04-28 2:56 ` [PATCH 5/6] sched/fair: Optimize __update_sched_avg() Yuyang Du
2016-04-28 2:56 ` [PATCH 6/6] documentation: Add scheuler/sched-avg.txt 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=1461812173-32439-5-git-send-email-yuyang.du@intel.com \
--to=yuyang.du@intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=pjt@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
all inboxes | Powered by JetHome®