From: Byungchul Park <byungchul.park@lge.com>
To: Juri Lelli <juri.lelli@arm.com>
Cc: peterz@infradead.org, mingo@kernel.org,
linux-kernel@vger.kernel.org, juri.lelli@gmail.com,
rostedt@goodmis.org, bristot@redhat.com, kernel-team@lge.com
Subject: Re: [PATCH v5 2/4] sched/deadline: Change return value of cpudl_find()
Date: Thu, 13 Jul 2017 10:24:21 +0900 [thread overview]
Message-ID: <20170713012420.GE20323@X58A-UD3R> (raw)
In-Reply-To: <20170712132232.kj6nxavxfglymsuy@e106622-lin>
On Wed, Jul 12, 2017 at 02:22:32PM +0100, Juri Lelli wrote:
> Hi,
>
> On 23/05/17 11:00, Byungchul Park wrote:
> > Currently cpudl_find() returns the best cpu that means it has the
> > maximum dl, however, the value is already kept in later_mask and the
> > return value is not referred directly any more.
> >
> > Now, it's enough to return whether CPUs were found or not, like rt.
> >
>
> I'd reword as
>
> cpudl_find() users are only interested in knowing if suitable CPU(s)
> were found or not (and then they look at later_mask to know which).
>
> Change cpudl_find() return type accordingly.
Hi,
Much better. Thank you very much. I will change it.
>
> > Signed-off-by: Byungchul Park <byungchul.park@lge.com>
> > ---
> > kernel/sched/cpudeadline.c | 26 +++++++++++++-------------
> > kernel/sched/deadline.c | 6 +++---
> > 2 files changed, 16 insertions(+), 16 deletions(-)
> >
> > diff --git a/kernel/sched/cpudeadline.c b/kernel/sched/cpudeadline.c
> > index fba235c..7408cbe 100644
> > --- a/kernel/sched/cpudeadline.c
> > +++ b/kernel/sched/cpudeadline.c
> > @@ -119,29 +119,29 @@ static inline int cpudl_maximum(struct cpudl *cp)
> > * @p: the task
> > * @later_mask: a mask to fill in with the selected CPUs (or NULL)
> > *
> > - * Returns: int - best CPU (heap maximum if suitable)
> > + * Returns: (int)bool - CPUs were found
>
> Why not simply bool?
I just did it same as rt.
> Thanks,
>
> - Juri
next prev parent reply other threads:[~2017-07-13 1:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 2:00 [PATCH v5 0/4] Make find_later_rq() choose a closer cpu in topology Byungchul Park
2017-05-23 2:00 ` [PATCH v5 1/4] sched/deadline: " Byungchul Park
2017-07-12 13:13 ` Juri Lelli
2017-07-13 1:38 ` Byungchul Park
2017-08-10 12:08 ` [tip:sched/core] sched/deadline: Make find_later_rq() choose a closer CPU " tip-bot for Byungchul Park
2017-05-23 2:00 ` [PATCH v5 2/4] sched/deadline: Change return value of cpudl_find() Byungchul Park
2017-07-12 13:22 ` Juri Lelli
2017-07-13 1:24 ` Byungchul Park [this message]
2017-08-10 12:08 ` [tip:sched/core] " tip-bot for Byungchul Park
2017-05-23 2:00 ` [PATCH v5 3/4] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq() Byungchul Park
2017-08-03 12:03 ` Peter Zijlstra
2017-08-04 5:16 ` Byungchul Park
2017-05-23 2:00 ` [PATCH v5 4/4] sched/rt: Add support for SD_PREFER_SIBLING on find_lowest_rq() Byungchul Park
2017-06-02 2:19 ` [PATCH v5 0/4] Make find_later_rq() choose a closer cpu in topology Byungchul Park
2017-07-12 2:44 ` 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=20170713012420.GE20323@X58A-UD3R \
--to=byungchul.park@lge.com \
--cc=bristot@redhat.com \
--cc=juri.lelli@arm.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®