From: Peter Zijlstra <peterz@infradead.org>
To: Patrick Bellasi <patrick.bellasi@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Paul Turner <pjt@google.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Juri Lelli <juri.lelli@redhat.com>, Todd Kjos <tkjos@android.com>,
Joel Fernandes <joelaf@google.com>
Subject: Re: [PATCH v2 2/4] sched/fair: add util_est on top of PELT
Date: Wed, 20 Dec 2017 10:02:41 +0100 [thread overview]
Message-ID: <20171220090241.jjsrs76phexy6fwd@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20171220085747.tgkle5b77z7yz4j4@hirez.programming.kicks-ass.net>
On Wed, Dec 20, 2017 at 09:57:47AM +0100, Peter Zijlstra wrote:
> On Fri, Dec 15, 2017 at 03:41:40PM +0000, Patrick Bellasi wrote:
> > Close enough, the actual code is:
> >
> > util_est = p->util_est.ewma;
> > 5218: f9403ba3 ldr x3, [x29,#112]
> > 521c: f9418462 ldr x2, [x3,#776]
> > if (abs(util_est - util_last) <= (SCHED_CAPACITY_SCALE / 100))
> > 5220: eb010040 subs x0, x2, x1
> > 5224: da805400 cneg x0, x0, mi
> > 5228: f100281f cmp x0, #0xa
> > 522c: 54fff9cd b.le 5164 <dequeue_task_fair+0xa04>
>
> Ah, that cneg instruction is cute; on x86 we end up with something like:
>
> bool abs_test(long s)
> {
> return abs(s) < 32;
> }
>
> cmpl $-31, %eax
> jl .L107
> movq -8(%rbp), %rax
> cmpl $31, %eax
> jg .L107
> movl $1, %eax
> jmp .L108
> .L107:
> movl $0, %eax
> .L108:
>
>
> But I figured you can actually do:
>
> abs(x) < y := (unsigned)(x + y - 1) < (2 * y - 1)
>
> Which, if y is a constant, should result in nicer code, and it does for
> x86:
>
> addq $31, %rax
> cmpq $62, %rax
> setbe %al
> movzbl %al, %eax
>
> Just not measurably faster, I suppose because of all the dependencies :/
Ah no, it actually is, I'm an idiot and used 'long' for return value. If
I use bool we loose that last movzbl and we go from around 4.0 cycles
down to 3.4 cycles.
next prev parent reply other threads:[~2017-12-20 9:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 17:10 [PATCH v2 0/4] Utilization estimation (util_est) for FAIR tasks Patrick Bellasi
2017-12-05 17:10 ` [PATCH v2 1/4] sched/fair: always used unsigned long for utilization Patrick Bellasi
2017-12-06 8:56 ` Vincent Guittot
2018-01-10 12:14 ` [tip:sched/core] sched/fair: Use 'unsigned long' for utilization, consistently tip-bot for Patrick Bellasi
2017-12-05 17:10 ` [PATCH v2 2/4] sched/fair: add util_est on top of PELT Patrick Bellasi
2017-12-13 16:05 ` Peter Zijlstra
2017-12-15 14:02 ` Patrick Bellasi
2017-12-15 14:07 ` Peter Zijlstra
2017-12-15 15:22 ` Patrick Bellasi
2017-12-13 16:16 ` Peter Zijlstra
2017-12-15 12:14 ` Patrick Bellasi
2017-12-15 12:53 ` Peter Zijlstra
2017-12-15 15:41 ` Patrick Bellasi
2017-12-20 8:57 ` Peter Zijlstra
2017-12-20 9:02 ` Peter Zijlstra [this message]
2017-12-13 16:19 ` Peter Zijlstra
2017-12-13 16:36 ` Patrick Bellasi
2017-12-13 17:03 ` Peter Zijlstra
2017-12-15 12:03 ` Patrick Bellasi
2017-12-15 12:58 ` Peter Zijlstra
2017-12-05 17:10 ` [PATCH v2 3/4] sched/fair: use util_est in LB and WU paths Patrick Bellasi
2017-12-05 17:10 ` [PATCH v2 4/4] sched/cpufreq_schedutil: use util_est for OPP selection Patrick Bellasi
2017-12-16 2:35 ` Rafael J. Wysocki
2017-12-18 10:48 ` Patrick Bellasi
2017-12-13 16:03 ` [PATCH v2 0/4] Utilization estimation (util_est) for FAIR tasks Peter Zijlstra
2017-12-13 16:23 ` Patrick Bellasi
2017-12-13 17:56 ` Mike Galbraith
2017-12-15 16:13 ` Patrick Bellasi
2017-12-15 20:23 ` Mike Galbraith
2017-12-16 6:37 ` Mike Galbraith
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=20171220090241.jjsrs76phexy6fwd@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dietmar.eggemann@arm.com \
--cc=joelaf@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=patrick.bellasi@arm.com \
--cc=pjt@google.com \
--cc=rafael.j.wysocki@intel.com \
--cc=tkjos@android.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@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®