From: Luca Abeni <luca.abeni@unitn.it>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: Wanpeng Li <wanpeng.li@hotmail.com>,
Juri Lelli <juri.lelli@arm.com>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] sched/deadline: fix earliest_dl.next logic
Date: Thu, 3 Dec 2015 09:37:51 +0100 [thread overview]
Message-ID: <565FFF5F.3000303@unitn.it> (raw)
In-Reply-To: <CANRm+CzxjBCgXzQ6QA8AvuDjqerNZV+cVszqNGMr3y4hx2Gt6A@mail.gmail.com>
Hi,
On 12/03/2015 03:25 AM, Wanpeng Li wrote:
[...]
>> @@ -202,16 +197,18 @@ static void dequeue_pushable_dl_task(struct rq *rq,
>> struct task_struct *p)
>>
>> next_node = rb_next(&p->pushable_dl_tasks);
>> dl_rq->pushable_dl_tasks_leftmost = next_node;
>> + if (next_node)
>> + dl_rq->earliest_dl.next = rb_entry(next_node,
>> + struct task_struct,
>> pushable_dl_tasks)->dl.deadline;
>
> Juri mentioned "updated leftmost", I'm not sure if it means that:
>
> @@ -195,6 +195,9 @@ static void dequeue_pushable_dl_task(struct rq
> *rq, struct task_struct *p)
>
> next_node = rb_next(&p->pushable_dl_tasks);
> dl_rq->pushable_dl_tasks_leftmost = next_node;
> + if (dl_rq->pushable_dl_tasks_leftmost)
> + dl_rq->earliest_dl.next =
> rb_entry(dl_rq->pushable_dl_tasks_leftmost,
> + struct task_struct,
> pushable_dl_tasks)->dl.deadline;
> }
This is basically the same thing I tested (I just used "next_node" instead
of "dl_rq->pushable_dl_tasks_leftmost" because the name is shorter), so I
think it should work.
Luca
next prev parent reply other threads:[~2015-12-03 8:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 11:47 [PATCH v5] sched/deadline: fix earliest_dl.next logic Wanpeng Li
2015-12-02 12:04 ` Juri Lelli
[not found] ` <BLU436-SMTP1847631AC50CA1AC2525A0F800E0@phx.gbl>
2015-12-02 14:08 ` Luca Abeni
2015-12-03 2:25 ` Wanpeng Li
2015-12-03 8:37 ` Luca Abeni [this message]
2015-12-03 8:59 ` Wanpeng Li
2015-12-03 9:22 ` Juri Lelli
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=565FFF5F.3000303@unitn.it \
--to=luca.abeni@unitn.it \
--cc=juri.lelli@arm.com \
--cc=kernellwp@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=wanpeng.li@hotmail.com \
/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