From: Valentin Schneider <valentin.schneider@arm.com>
To: Beata Michalska <beata.michalska@arm.com>, linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [RFC PATCH v2 0/3] Rework CPU capacity asymmetry detection
Date: Wed, 05 May 2021 19:17:55 +0100 [thread overview]
Message-ID: <87bl9pxcx8.mognet@arm.com> (raw)
In-Reply-To: <1619602363-1305-1-git-send-email-beata.michalska@arm.com>
On 28/04/21 10:32, Beata Michalska wrote:
> v2:
> - Fixed style issues
> - Reworked accessing the cached topology data as suggested by Valentin
>
Other than my pedantic nitpicks:
Tested-by: Valentin Schneider <valentin.schneider@arm.com>
Reviewed-by: Valentin Schneider <valentin.schneider@arm.com>
Thanks for tackling this!
> Beata Michalska (3):
> sched/core: Introduce SD_ASYM_CPUCAPACITY_FULL sched_domain flag
> sched/topology: Rework CPU capacity asymmetry detection
> sched/doc: Update the CPU capacity asymmetry bits
>
> Documentation/scheduler/sched-capacity.rst | 6 +-
> Documentation/scheduler/sched-energy.rst | 2 +-
> include/linux/sched/sd_flags.h | 10 +
> kernel/sched/topology.c | 327 +++++++++++++++++++++++++----
> 4 files changed, 302 insertions(+), 43 deletions(-)
>
> --
> 2.7.4
prev parent reply other threads:[~2021-05-05 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 9:32 [RFC PATCH v2 0/3] Rework CPU capacity asymmetry detection Beata Michalska
2021-04-28 9:32 ` [RFC PATCH v2 1/3] sched/core: Introduce SD_ASYM_CPUCAPACITY_FULL sched_domain flag Beata Michalska
2021-04-28 9:32 ` [RFC PATCH v2 2/3] sched/topology: Rework CPU capacity asymmetry detection Beata Michalska
2021-05-05 18:17 ` Valentin Schneider
2021-04-28 9:32 ` [RFC PATCH v2 3/3] sched/doc: Update the CPU capacity asymmetry bits Beata Michalska
2021-04-28 17:19 ` Randy Dunlap
2021-05-10 16:33 ` Beata Michalska
2021-05-05 18:17 ` Valentin Schneider [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=87bl9pxcx8.mognet@arm.com \
--to=valentin.schneider@arm.com \
--cc=beata.michalska@arm.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).