From: Juri Lelli <juri.lelli@arm.com>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: Luca Abeni <luca.abeni@unitn.it>,
Wanpeng Li <wanpeng.li@hotmail.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:22:52 +0000 [thread overview]
Message-ID: <20151203092252.GA20439@e106622-lin> (raw)
In-Reply-To: <CANRm+Cz6FA1gOTnVqGD+wdKVptwY72DAY1B1HzX1pd4tCBv5_w@mail.gmail.com>
Hi,
On 03/12/15 16:59, Wanpeng Li wrote:
> 2015-12-03 16:37 GMT+08:00 Luca Abeni <luca.abeni@unitn.it>:
> > 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.
>
> Yeah, the same, what I want to know is Juri's choice. Ping Juri, :-)
>
IMHO, Luca's solution looks shorter/better :-).
Thanks,
- Juri
prev parent reply other threads:[~2015-12-03 9:22 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
2015-12-03 8:59 ` Wanpeng Li
2015-12-03 9:22 ` Juri Lelli [this message]
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=20151203092252.GA20439@e106622-lin \
--to=juri.lelli@arm.com \
--cc=kernellwp@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@unitn.it \
--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