From: 王擎 <wangqing@vivo.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
"dietmar.eggemann@arm.com" <dietmar.eggemann@arm.com>,
Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Subject: [PATCH V2 0/2] Add complex scheduler level for arm64
Date: Tue, 26 Apr 2022 07:05:15 +0000 [thread overview]
Message-ID: <SL2PR06MB30828131C046AB979BE75BD6BDFB9@SL2PR06MB3082.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <SL2PR06MB3082D393ADEC823426DEE7DFBDFB9@SL2PR06MB3082.apcprd06.prod.outlook.com>
Hi Sudeep:
I am thinking if it is possible to add a complex level cpu topology
between cluster and SMT?
We can describe it directly in “cpu-map”, instead of parsing it through
the cache info.
Thanks,
Qing
>>> From: Wang Qing <wangqing@vivo.com>
>>>
>>> The DSU cluster supports blocks that are called complexes
>>> which contain up to two cores of the same type and some shared logic,
>>> which sharing some logic between the cores can make a complex area efficient.
>>>
>>
>>Given the complex shares things like the SVE units (cortex a510)...
>>
>>Why not handle this as SMT?
>
>SMT should share all cache levels. but complexs only share L2(and L3)
>cache here.
>
>>
>>Seems like a blurred boundary between separate cores and SMT threads.
>>I think we need to express and potentially take advantage of knowledge
>>about what logic is being shared.
>
>Logic such as a Vector Processing Unit, L2 Translation Lookaside Buffer
>(TLB) ... are shared, I believe this will improve efficiency even if
>only L2 cache is shared.
>
>Thanks,
>Qing
>
>>
>>Jonathan
>>
>>> Complex also can be considered as a shared cache group smaller
>>> than cluster.
>>>
>>> This patch adds complex level for complexs by parsing cache topology
>>> form DT. It will directly benefit a lot of workload which loves more
>>> resources such as memory bandwidth, caches.
>>>
>>> Note this patch only handle the DT case.
>>>
>>> V2:
>>> fix commit log and loop more
>>>
>>> wangqing (2):
>>> arch_topology: support for describing cache topology from DT
>>> arm64: Add complex scheduler level for arm64
>>>
>>> arch/arm64/Kconfig | 13 ++++++++++
>>> arch/arm64/kernel/smp.c | 48 ++++++++++++++++++++++++++++++++++-
>>> drivers/base/arch_topology.c | 47 +++++++++++++++++++++++++++++++++-
>>> include/linux/arch_topology.h | 3 +++
>>> 4 files changed, 109 insertions(+), 2 deletions(-)
>>>
next prev parent reply other threads:[~2022-04-26 7:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 11:51 Qing Wang
2022-04-22 11:51 ` [PATCH V2 1/2] arch_topology: support for parsing cache topology from DT Qing Wang
2022-04-22 12:30 ` Greg Kroah-Hartman
2022-04-24 2:53 ` [PATCH V2 RESEND " 王擎
2022-04-22 11:51 ` [PATCH V2 2/2] arm64: Add complex scheduler level for arm64 Qing Wang
2022-04-22 12:31 ` Greg Kroah-Hartman
2022-04-24 2:26 ` 王擎
2022-04-26 18:15 ` kernel test robot
2022-04-25 13:19 ` [PATCH V2 0/2] " Jonathan Cameron
2022-04-26 3:06 ` 王擎
2022-04-26 7:05 ` 王擎 [this message]
2022-04-26 13:27 ` Sudeep Holla
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=SL2PR06MB30828131C046AB979BE75BD6BDFB9@SL2PR06MB3082.apcprd06.prod.outlook.com \
--to=wangqing@vivo.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=catalin.marinas@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=will@kernel.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®