From: luca abeni <luca.abeni@unitn.it>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@arm.com>
Subject: Re: [RFC v2 3/7] Improve the tracking of active utilisation
Date: Tue, 5 Apr 2016 21:35:49 +0200 [thread overview]
Message-ID: <20160405213549.244169ca@utopia> (raw)
In-Reply-To: <20160405180050.GO3408@twins.programming.kicks-ass.net>
On Tue, 5 Apr 2016 20:00:50 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> On Tue, Apr 05, 2016 at 07:56:57PM +0200, luca abeni wrote:
> > > > + if (rq != cpu_rq(cpu)) {
> > >
> > > I don't think this is right, you want:
> > >
> > > if (task_cpu(p) != cpu) {
> > >
> > > because @cpu does not need to be task_cpu().
> > Uhm... I must have misunderstood something in the code, then :(
> > What I want to do here is to check if select_task_rq_dl() selected
> > a new CPU for this task... Since at the beginning of the function
> > rq is set as
> > rq = cpu_rq(cpu);
> > I was thinkint about checking if this is still true (if not, it
> > means that the value of "cpu" changed).
> >
> > I'll look at it again.
>
> Basically because:
>
> ac66f5477239 ("sched/numa: Introduce migrate_swap()")
Thanks; I am going to look at it
Thanks,
Luca
>
> we cannot (in general) assume .cpu == task_cpu(p).
>
> Now it might still be true for deadline tasks, but I find it easier to
> simply not rely on such assumptions.
next prev parent reply other threads:[~2016-04-05 19:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 15:12 [RFC v2 0/7] CPU reclaiming for SCHED_DEADLINE Luca Abeni
2016-04-01 15:12 ` [RFC v2 1/7] Track the active utilisation Luca Abeni
2016-04-05 12:23 ` Peter Zijlstra
2016-04-05 16:47 ` luca abeni
2016-04-01 15:12 ` [RFC v2 2/7] Correctly track the active utilisation for migrating tasks Luca Abeni
2016-04-05 12:24 ` Peter Zijlstra
2016-04-05 16:50 ` luca abeni
2016-04-01 15:12 ` [RFC v2 3/7] Improve the tracking of active utilisation Luca Abeni
2016-04-05 12:42 ` Peter Zijlstra
2016-04-05 17:00 ` luca abeni
2016-04-05 12:42 ` Peter Zijlstra
2016-04-05 17:05 ` luca abeni
2016-04-05 14:48 ` Peter Zijlstra
2016-04-05 17:17 ` luca abeni
2016-04-05 15:00 ` Peter Zijlstra
2016-04-05 17:56 ` luca abeni
2016-04-05 18:00 ` Peter Zijlstra
2016-04-05 19:35 ` luca abeni [this message]
2016-04-05 18:02 ` Peter Zijlstra
2016-04-05 19:24 ` luca abeni
2016-04-05 19:31 ` Peter Zijlstra
2016-04-05 19:32 ` luca abeni
2016-04-05 18:11 ` Peter Zijlstra
2016-04-01 15:12 ` [RFC v2 4/7] Fix the update of the total -deadline utilization Luca Abeni
2016-04-05 12:58 ` Peter Zijlstra
2016-04-05 17:16 ` luca abeni
2016-04-01 15:12 ` [RFC v2 5/7] GRUB accounting Luca Abeni
2016-04-01 15:12 ` [RFC v2 6/7] Make GRUB a task's flag Luca Abeni
2016-04-01 15:12 ` [RFC v2 7/7] Do not reclaim the whole CPU bandwidth Luca Abeni
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=20160405213549.244169ca@utopia \
--to=luca.abeni@unitn.it \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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