From: Vincent Guittot <vincent.guittot@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Morten Rasmussen <Morten.Rasmussen@arm.com>,
Patrick Bellasi <patrick.bellasi@arm.com>,
Paul Turner <pjt@google.com>, Ben Segall <bsegall@google.com>,
Thara Gopinath <thara.gopinath@linaro.org>
Subject: Re: [PATCH v4 2/2] sched/fair: update scale invariance of PELT
Date: Tue, 23 Oct 2018 14:15:46 +0200 [thread overview]
Message-ID: <CAKfTPtAVODuDsvFsGpdnxQjGffOa=WKBEcnqo-vGkmaMs=UcAQ@mail.gmail.com> (raw)
In-Reply-To: <20181023100057.GJ3109@worktop.c.hoisthospitality.com>
On Tue, 23 Oct 2018 at 12:01, Peter Zijlstra <peterz@infradead.org> wrote:
>
> On Fri, Oct 19, 2018 at 06:17:51PM +0200, Vincent Guittot wrote:
> > In order to achieve this time scaling, a new clock_pelt is created per rq.
>
>
> > diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
> > index 3990818..d987f50 100644
> > --- a/kernel/sched/sched.h
> > +++ b/kernel/sched/sched.h
> > @@ -848,6 +848,8 @@ struct rq {
> > unsigned int clock_update_flags;
> > u64 clock;
> > u64 clock_task;
> > + u64 clock_pelt;
> > + unsigned long lost_idle_time;
>
> Very clever that. Seems to work out nicely. We should maybe look at
Thanks
> ensuring all these clock fields are indeed on the same cacheline.
yes good point
next prev parent reply other threads:[~2018-10-23 12:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 16:17 [PATCH v4 0/2] sched/fair: update scale invariance of PELT Vincent Guittot
2018-10-19 16:17 ` [PATCH 1/2] sched/fair: move rq_of helper function Vincent Guittot
2018-10-20 0:44 ` kbuild test robot
2018-10-19 16:17 ` [PATCH v4 2/2] sched/fair: update scale invariance of PELT Vincent Guittot
2018-10-23 5:59 ` Pavan Kondeti
2018-10-23 12:15 ` Vincent Guittot
2018-10-24 4:53 ` Pavan Kondeti
2018-10-24 9:07 ` Vincent Guittot
2018-10-23 10:00 ` Peter Zijlstra
2018-10-23 12:15 ` Vincent Guittot [this message]
2018-10-25 10:35 ` Dietmar Eggemann
2018-10-25 10:43 ` Vincent Guittot
2018-10-25 11:08 ` Dietmar Eggemann
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='CAKfTPtAVODuDsvFsGpdnxQjGffOa=WKBEcnqo-vGkmaMs=UcAQ@mail.gmail.com' \
--to=vincent.guittot@linaro.org \
--cc=Morten.Rasmussen@arm.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rjw@rjwysocki.net \
--cc=thara.gopinath@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;
as well as URLs for NNTP newsgroup(s).