From: Beata Michalska <beata.michalska@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
juri.lelli@redhat.com, vincent.guittot@linaro.org,
valentin.schneider@arm.com, dietmar.eggemann@arm.com,
corbet@lwn.net, rdunlap@infradead.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 2/3] sched/topology: Rework CPU capacity asymmetry detection
Date: Thu, 13 May 2021 15:01:43 +0100 [thread overview]
Message-ID: <20210513140141.GC15289@e120325.cambridge.arm.com> (raw)
In-Reply-To: <YJ0wuY1uDVbvTxRT@hirez.programming.kicks-ass.net>
On Thu, May 13, 2021 at 03:59:21PM +0200, Peter Zijlstra wrote:
> On Thu, May 13, 2021 at 02:48:32PM +0100, Beata Michalska wrote:
>
> > > > Where:
> > > > arch_scale_cpu_capacity(L) = 512
> > > > arch_scale_cpu_capacity(M) = 871
> > > > arch_scale_cpu_capacity(B) = 1024
> > >
> > > Low, High
> > > Small, Big
> > >
> > > But you appear to have picked: Low and Big, which just doesn't make any
> > > sense. (Worse, L can also be Large :-)
> > >
> > (L)ittle, (M)edium, (B)ig
> > I can re-arrange the abbreviations used here.
>
> Duh, I must really be having a bad day for not thinking of Little. I
> don't think you need to change this. S,M,L would be like a clothing
> store, but steps away from the big.Little thing.
>
That's how I would prefer it - keep the 'little' things
Thanks
---
BR
B.
next prev parent reply other threads:[~2021-05-13 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 16:30 [PATCH v3 0/3] Rework CPU capacity asymmetry detection Beata Michalska
2021-05-10 16:30 ` [PATCH v3 1/3] sched/core: Introduce SD_ASYM_CPUCAPACITY_FULL sched_domain flag Beata Michalska
2021-05-10 16:30 ` [PATCH v3 2/3] sched/topology: Rework CPU capacity asymmetry detection Beata Michalska
2021-05-13 11:05 ` Peter Zijlstra
2021-05-13 13:48 ` Beata Michalska
2021-05-13 13:59 ` Peter Zijlstra
2021-05-13 14:01 ` Beata Michalska [this message]
2021-05-10 16:30 ` [PATCH v3 3/3] sched/doc: Update the CPU capacity asymmetry bits Beata Michalska
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=20210513140141.GC15289@e120325.cambridge.arm.com \
--to=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=rdunlap@infradead.org \
--cc=valentin.schneider@arm.com \
--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).