From: sashiko-bot@kernel.org
To: "Mete Durlu" <meted@linux.ibm.com>
Cc: "Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
linux-s390@vger.kernel.org, "Vasily Gorbik" <gor@linux.ibm.com>
Subject: Re: [PATCH] s390/topology: Enable ASYM_PACKING to establish cpu priority
Date: Tue, 01 Sep 2026 14:52:24 +0000 [thread overview]
Message-ID: <20260901145224.EA1411F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260901-s390_sd_flags-v1-1-6755ba191d5a@linux.ibm.com>
> On s390 LPARs the hypervisor assigns varying CPU runtime capacities
> under vertical polarization, making CPUs unequal. Add SD_ASYM_PACKING
> into topology level flag callbacks so the scheduler keeps busier
> scheduling groups packed onto higher-capacity CPUs.
> Implement arch_asym_cpu_priority() using smp_cpu_get_capacity() as
> the decision factor. Subtract the CPU number so that the CPUs with
> lower ids are prioritized.
>
> Only enabled on LPAR level as other guest levels either do not have
> vertical polarization (which causes asymmetric CPUs), or machine backed
> topology.
>
> Signed-off-by: Mete Durlu <meted@linux.ibm.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260901-s390_sd_flags-v1-1-6755ba191d5a@linux.ibm.com?part=1
next prev parent reply other threads:[~2026-09-01 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 14:40 [PATCH] s390/topology: Enable ASYM_PACKING to establish cpu priority Mete Durlu
2026-09-01 14:52 ` sashiko-bot [this message]
2026-09-01 15:30 ` Heiko Carstens
2026-09-03 11:46 ` Mete Durlu
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=20260901145224.EA1411F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=meted@linux.ibm.com \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.