From: Peter Zijlstra <peterz@infradead.org>
To: Douglas Raillard <douglas.raillard@arm.com>
Cc: Patrick Bellasi <patrick.bellasi@arm.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Quentin Perret <quentin.perret@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Juri Lelli <juri.lelli@redhat.com>
Subject: Re: [PATCH] sched/fair: util_est: fast ramp-up EWMA on utilization increases
Date: Thu, 17 Oct 2019 10:25:37 +0200 [thread overview]
Message-ID: <20191017082537.GX2328@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <48adc956-77a4-e293-29d9-cd8b82a40ae8@arm.com>
On Mon, Oct 14, 2019 at 05:16:02PM +0100, Douglas Raillard wrote:
> random idea: Since these things are much easier to understand by looking at a graph
> of util over time, we may agree on some mailing-list-friendly way to convey graphs.
I don't think that this patch warrants something like that. It is fairly
clear what it does.
For other stuff, maybe.
> For example, a simple CSV with:
> * before/after delimiters (line of # or =)
> * graph title
> * one point per signal transition, so that it can be plotted with gnuplot style "steps" or matplotlib drawstyle='steps-post'
> * consistent column names:
> - time: in seconds (scientific notation for nanoseconds)
> - activation: 1 when the task is actually running, 0 otherwise
> (so it can be turned into transparent coloured bands like using gnuplot filledcurves, like in [1])
> - util: util_avg of the task being talked about
>
> The delimiters allow writing a scripts to render graphs directly out of an mbox file or ML archive URL.
> This won't solve the issue for the commit message itself, but that may ease the ML discussions.
Something like that could work; mutt can easily pipe emails into
scripts. OTOH gnuplot also has ASCII output, so one can easily stick
something like that into email.
next prev parent reply other threads:[~2019-10-17 8:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 15:05 [PATCH] sched/fair: util_est: fast ramp-up EWMA on utilization increases Patrick Bellasi
2019-06-26 11:40 ` Vincent Guittot
2019-06-28 10:08 ` Patrick Bellasi
2019-06-28 12:38 ` Peter Zijlstra
2019-06-28 13:51 ` Vincent Guittot
2019-06-28 14:10 ` Patrick Bellasi
2019-06-30 8:43 ` Vincent Guittot
2019-07-01 8:53 ` Patrick Bellasi
2019-06-28 14:00 ` Patrick Bellasi
2019-08-02 9:47 ` Patrick Bellasi
2019-10-14 14:52 ` Peter Zijlstra
2019-10-14 14:57 ` Vincent Guittot
2019-10-14 16:16 ` Douglas Raillard
2019-10-17 8:25 ` Peter Zijlstra [this message]
2019-10-21 6:19 ` Patrick Bellasi
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=20191017082537.GX2328@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dietmar.eggemann@arm.com \
--cc=douglas.raillard@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=patrick.bellasi@arm.com \
--cc=quentin.perret@arm.com \
--cc=rafael.j.wysocki@intel.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