public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Joel Fernandes <joelaf@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@arm.com>,
	Brendan Jackman <brendan.jackman@arm.com>,
	Dietmar Eggeman <dietmar.eggemann@arm.com>,
	kernel-team@android.com, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v2] sched/fair: Make PELT signal more accurate
Date: Sun, 20 Aug 2017 08:00:25 +0200	[thread overview]
Message-ID: <1503208825.12180.125.camel@gmx.de> (raw)
In-Reply-To: <CAJWu+opJiVMGfBCTYfKr=V5v_xA+8mAEzE7w8kfKXNk-HPsuTQ@mail.gmail.com>

On Sat, 2017-08-19 at 10:58 -0700, Joel Fernandes wrote:
> 
> > Ok, I gotta ask:  In order to fix what?  What exactly does the small
> > but existent overhead increase buy us other than an ever so slightly
> > different chart?  What is your motivation to care about a microscopic
> > change in signal shape?
> 
> I wouldn't call the change "microscopic", its about 2% absolute which
> comes down to 1% with this change (if you count in relative terms, its
> higher and you can see the bump as the signal rises).
> If you look at the first chart at [1] at 3.74, that's not microscopic
> at all to me.

Whether that 0.02->0.01 is viewed as significant by you or I matters
not at all, for it to be significant, it must have measurable effect. 

Where is the consumer which benefits from precision improvement.. of
the instantaneously wildly inaccurate average.  Where is the non-zero
return on investment?  If the chart is the entire product, no sale.

	-Mike

  reply	other threads:[~2017-08-20  6:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18 23:50 [PATCH v2] sched/fair: Make PELT signal more accurate Joel Fernandes
2017-08-19  4:57 ` Mike Galbraith
2017-08-19 17:58   ` Joel Fernandes
2017-08-20  6:00     ` Mike Galbraith [this message]
2017-08-20  6:46       ` Joel Fernandes

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=1503208825.12180.125.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=brendan.jackman@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=joelaf@google.com \
    --cc=juri.lelli@arm.com \
    --cc=kernel-team@android.com \
    --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