From: Byungchul Park <byungchul.park@lge.com>
To: "Joel Fernandes (Google)" <joel.opensrc@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
mingo@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
juri.lelli@gmail.com, rostedt@goodmis.org, kernel-team@lge.com
Subject: Re: [PATCH v6 0/2] Make find_later_rq() choose a closer cpu in topology
Date: Fri, 18 Aug 2017 14:34:55 +0900 [thread overview]
Message-ID: <20170818053455.GA20323@X58A-UD3R> (raw)
In-Reply-To: <CAEi0qN=i7ZCmzrEKQ1DWTjx4FB3gZVUzJ6bTgb4HLU09k0C9dw@mail.gmail.com>
On Thu, Aug 17, 2017 at 09:51:34PM -0700, Joel Fernandes (Google) wrote:
> On Thu, Aug 17, 2017 at 6:25 PM, Byungchul Park <byungchul.park@lge.com> wrote:
> > On Mon, Aug 07, 2017 at 12:50:32PM +0900, Byungchul Park wrote:
> >> When cpudl_find() returns any among free_cpus, the cpu might not be
> >> closer than others, considering sched domain. For example:
> >>
> >> this_cpu: 15
> >> free_cpus: 0, 1,..., 14 (== later_mask)
> >> best_cpu: 0
> >>
> >> topology:
> >>
> >> 0 --+
> >> +--+
> >> 1 --+ |
> >> +-- ... --+
> >> 2 --+ | |
> >> +--+ |
> >> 3 --+ |
> >>
> >> ... ...
> >>
> >> 12 --+ |
> >> +--+ |
> >> 13 --+ | |
> >> +-- ... -+
> >> 14 --+ |
> >> +--+
> >> 15 --+
> >>
> >> In this case, it would be best to select 14 since it's a free cpu and
> >> closest to 15(this_cpu). However, currently the code select 0(best_cpu)
> >> even though that's just any among free_cpus. Fix it.
> >
> > Could you let me know your opinions about this?
>
> Patch looks good to me, I would also add a comment ontop of
> fallback_cpu (I think Steve mentioned similar thing at [1])
>
> /*
> * fallback is the closest CPU in the closest SD incase
> * all domains are PREFER_SIBLING
> */
> if (fallback_cpu == -1)
> fallback_cpu = best_cpu;
>
> And clarify this in the commit message.
Right. I will add it.
Thank you very much,
Byungchul
prev parent reply other threads:[~2017-08-18 5:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 3:50 Byungchul Park
2017-08-07 3:50 ` [PATCH v6 1/2] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq() Byungchul Park
2017-08-15 15:19 ` Steven Rostedt
2017-08-16 0:38 ` Byungchul Park
2017-08-16 1:42 ` Steven Rostedt
2017-08-16 2:17 ` Byungchul Park
2017-08-16 13:32 ` Steven Rostedt
2017-08-16 14:04 ` Byungchul Park
2017-08-16 14:25 ` Steven Rostedt
2017-08-07 3:50 ` [PATCH v6 2/2] sched/rt: Add support for SD_PREFER_SIBLING on find_lowest_rq() Byungchul Park
2017-08-10 12:12 ` Byungchul Park
2017-08-18 1:25 ` [PATCH v6 0/2] Make find_later_rq() choose a closer cpu in topology Byungchul Park
2017-08-18 4:51 ` Joel Fernandes (Google)
2017-08-18 5:34 ` Byungchul Park [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=20170818053455.GA20323@X58A-UD3R \
--to=byungchul.park@lge.com \
--cc=joel.opensrc@gmail.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®