From: Byungchul Park <byungchul.park@lge.com>
To: Daniel Bristot de Oliveira <bristot@redhat.com>,
peterz@infradead.org, mingo@kernel.org, rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, juri.lelli@gmail.com, kernel-team@lge.com
Subject: Re: [RESEND PATCH v2 2/2] sched/deadline: Initialize cp->elements[].cpu to an invalid value
Date: Tue, 14 Nov 2017 08:30:54 +0900 [thread overview]
Message-ID: <deeb992a-cf45-7168-a292-6fcaaf8343c1@lge.com> (raw)
In-Reply-To: <30b71aa6-4662-7056-1a09-a88f4143d1d1@redhat.com>
On 11/13/2017 9:46 PM, Daniel Bristot de Oliveira wrote:
> On 10/12/2017 09:57 AM, Byungchul Park wrote:
>> On Tue, Oct 10, 2017 at 03:44:04PM +0900, Byungchul Park wrote:
>>> Currently, migrating tasks to cpu0 unconditionally happens when the
>>> heap is empty, since cp->elements[].cpu was initialized to 0(=cpu0).
>>> We have to distinguish between the empty case and cpu0 to avoid the
>>> unnecessary migrantions. Therefore, it has to return an invalid value
>
> s/migrantions/migrations/ ?
>
>>> e.i. -1 in that case.
>>
>> This patch does what it should obviously do. Could you check this?
>>
>>> Signed-off-by: Byungchul Park <byungchul.park@lge.com>
>>> Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
>>> ---
>>> kernel/sched/cpudeadline.c | 10 +++++++++-
>>> 1 file changed, 9 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/kernel/sched/cpudeadline.c b/kernel/sched/cpudeadline.c
>>> index 9f02035..bcf903f 100644
>>> --- a/kernel/sched/cpudeadline.c
>>> +++ b/kernel/sched/cpudeadline.c
>>> @@ -138,6 +138,12 @@ int cpudl_find(struct cpudl *cp, struct task_struct *p,
>>> int best_cpu = cpudl_maximum_cpu(cp);
>>> WARN_ON(best_cpu != -1 && !cpu_present(best_cpu));
>>>
>>> + /*
>>> + * The heap tree is empry for now, just return.
>
> s/empry/empty/ ?
Hello Daniel,
Thank you very much for pointing out typos.
I shall do spellcheck evetytime submiting patches from now on.
--
Thanks,
Byungchul
next prev parent reply other threads:[~2017-11-13 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 6:44 [RESEND PATCH v2 1/2] sched/deadline: Add cpudl_maximum_dl() for clean-up Byungchul Park
2017-10-10 6:44 ` [RESEND PATCH v2 2/2] sched/deadline: Initialize cp->elements[].cpu to an invalid value Byungchul Park
2017-10-12 7:57 ` Byungchul Park
2017-11-13 12:46 ` Daniel Bristot de Oliveira
2017-11-13 23:30 ` Byungchul Park [this message]
2017-10-23 8:43 ` [RESEND PATCH v2 1/2] sched/deadline: Add cpudl_maximum_dl() for clean-up Byungchul Park
2017-10-27 8:38 ` Byungchul Park
2017-11-13 11:00 ` Daniel Bristot de Oliveira
2017-11-02 1:25 Byungchul Park
2017-11-02 1:25 ` [RESEND PATCH v2 2/2] sched/deadline: Initialize cp->elements[].cpu to an invalid value Byungchul Park
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=deeb992a-cf45-7168-a292-6fcaaf8343c1@lge.com \
--to=byungchul.park@lge.com \
--cc=bristot@redhat.com \
--cc=juri.lelli@gmail.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®