From: Valentin Schneider <valentin.schneider@arm.com>
To: Qais Yousef <qais.yousef@arm.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
peterz@infradead.org, Dietmar.Eggemann@arm.com,
morten.rasmussen@arm.com
Subject: Re: [PATCH 1/2] sched/topology: build_sched_groups: Skip duplicate group rewrites
Date: Wed, 10 Apr 2019 11:17:15 +0100 [thread overview]
Message-ID: <ab929846-4f05-0ce9-c159-7f560a7edfca@arm.com> (raw)
In-Reply-To: <20190410092723.d4j4ctccogprtptg@e107158-lin.cambridge.arm.com>
On 10/04/2019 10:27, Qais Yousef wrote:
[...]
>> @@ -1066,9 +1067,14 @@ static struct sched_group *get_group(int cpu, struct sd_data *sdd)
>> sg = *per_cpu_ptr(sdd->sg, cpu);
>> sg->sgc = *per_cpu_ptr(sdd->sgc, cpu);
>>
>> - /* For claim_allocations: */
>> - atomic_inc(&sg->ref);
>> - atomic_inc(&sg->sgc->ref);
>> + /* Increase refcounts for claim_allocations: */
>> + already_visited = atomic_inc_return(&sg->ref) > 1;
>> + /* sgc visits should follow a similar trend as sg */
>> + WARN_ON(already_visited != (atomic_inc_return(&sg->sgc->ref) > 1));
>
> NIT: I think it would be better to not have any side effect of calling
> WARN_ON(). Ie: do the atomic_inc_return() outside the WARN_ON() condition.
> Having two bool already_visited_sg and already_visited_sgc will make the code
> more readable too.
>
I agree it's not the nicest reading flow there is. It's already gone in
tip/sched/core but if needed I can resend with this extra separation.
> Thanks
>
> --
> Qais Yousef
>
>> +
>> + /* If we have already visited that group, it's already initialized. */
>> + if (already_visited)
>> + return sg;
>>
>> if (child) {
>> cpumask_copy(sched_group_span(sg), sched_domain_span(child));
>> --
>> 2.20.1
>>
next prev parent reply other threads:[~2019-04-10 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 17:35 [PATCH 0/2] sched/topology: Small fixes Valentin Schneider
2019-04-09 17:35 ` [PATCH 1/2] sched/topology: build_sched_groups: Skip duplicate group rewrites Valentin Schneider
2019-04-10 9:27 ` Qais Yousef
2019-04-10 10:17 ` Valentin Schneider [this message]
2019-04-10 10:31 ` Qais Yousef
2019-04-09 17:35 ` [PATCH 2/2] sched/topology: Fix build_sched_groups() comment Valentin Schneider
2019-04-10 8:46 ` [tip:sched/core] " tip-bot for Valentin Schneider
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=ab929846-4f05-0ce9-c159-7f560a7edfca@arm.com \
--to=valentin.schneider@arm.com \
--cc=Dietmar.Eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.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
all inboxes | Powered by JetHome®