From: Steven Rostedt <rostedt@goodmis.org>
To: Byungchul Park <byungchul.park@lge.com>
Cc: peterz@infradead.org, mingo@kernel.org,
linux-kernel@vger.kernel.org, juri.lelli@gmail.com,
kernel-team@lge.com
Subject: Re: [PATCH v6 1/2] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq()
Date: Tue, 15 Aug 2017 21:42:01 -0400 [thread overview]
Message-ID: <20170815214201.15b6424b@gandalf.local.home> (raw)
In-Reply-To: <20170816003810.GO20323@X58A-UD3R>
On Wed, 16 Aug 2017 09:38:11 +0900
Byungchul Park <byungchul.park@lge.com> wrote:
> On Tue, Aug 15, 2017 at 11:19:40AM -0400, Steven Rostedt wrote:
> > > @@ -1385,6 +1407,17 @@ static int find_later_rq(struct task_struct *task)
> > > * already under consideration through later_mask.
> > > */
> > > if (best_cpu < nr_cpu_ids) {
> > > + /*
> > > + * If current domain is SD_PREFER_SIBLING
> > > + * flaged, we have to get more chances to
> > > + * check other siblings.
BTW, "we have to get more chances" doesn't really make sense. Do you
mean "we need to try other domains"?
> > > + */
> > > + if (sd->flags & SD_PREFER_SIBLING) {
> > > + prefer = sd;
> >
> > Is this how the SD_PREFER_SIBLING works? According to this, the
> > preferred sd is the next sd in for_each_domain(). Not to mention, the
> > prefer variable stays set if the next domain has no available CPUs. Is
> > that what we want?
>
> Maybe I don't understand what you want to say. The variable, prefer, is
> used to pick up the smallest sched domain among SD_PREFER_SIBLING
> domains, if more than one SD_PREFER_SIBLING domain exist in the visit.
>
> The prefer variable alway points to the previous SD_PREFER_SIBLING domain.
> And that must stay set to be used as a fallback choise if the next domain
> has no available CPUs.
>
> Could you explain what I mis-understand?
>
I may be the one confused here ;-)
I think I misread the patch. So, the SD_PREFER_SIBLING means to try to
find a CPU in another sd instead? Thus, we try to find a CPU in a sd
that does not have SD_PREFER_SIBLING set. And if there is none, we use
the preferred sd as a fallback. Is that correct?
I'm not familiar with the SD_PREFER_SIBLING flag, the only
documentation I can find about it is the comment that states:
/* Prefer to place tasks in a sibling domain */
And the very informative git commit change log:
commit b5d978e0c7e79a7ff842e895c85a86b38c71f1cd
Date: Tue Sep 1 10:34:33 2009 +0200
sched: Add SD_PREFER_SIBLING
Do the placement thing using SD flags.
;-)
-- Steve
next prev parent reply other threads:[~2017-08-16 1:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 3:50 [PATCH v6 0/2] Make find_later_rq() choose a closer cpu in topology 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 [this message]
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
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=20170815214201.15b6424b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=byungchul.park@lge.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 \
/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