From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Xuewen Yan <xuewen.yan94@gmail.com>,
Christian Loehle <christian.loehle@arm.com>
Cc: Xuewen Yan <xuewen.yan@unisoc.com>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
vdonnefort@google.com, ke.wang@unisoc.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] sched/feec: Simplify the traversal of pd'cpus
Date: Fri, 15 Aug 2025 14:01:39 +0100 [thread overview]
Message-ID: <8a84e658-1c2d-4380-8979-e1cc5bf5768d@arm.com> (raw)
In-Reply-To: <CAB8ipk9BDzsTTcdRKc9R_Hc72cOY8YyUfrCoY3_9hPJ8D-Fg_Q@mail.gmail.com>
On 14.08.25 10:52, Xuewen Yan wrote:
> Hi Dietmar,
>
> On Thu, Aug 14, 2025 at 4:46 PM Dietmar Eggemann
> <dietmar.eggemann@arm.com> wrote:
>>
>> On 12.08.25 10:33, Xuewen Yan wrote:
[...]
>> Can you not mask cpus already early in the pd loop (1) and then profit
>> from (2) in these rare cases?
>
> I do not think the cpus_ptr chould place before the pd_cap calc,
> because the following scenario should be considered:
> the task's cpus_ptr cpus: 0,1,2,3
> pd's cpus: 0,1,2,3,4,5,6
> the pd's cap = cpu_cap * 6;
> if we cpumask_and(pd'scpus, p->cpus_ptr),
> the cpumask_weight = 4,
> the pd's cap = cpu_cap *4.
Yes, you're right! Missed this one.
>> IIRC, the sd only plays a role here in
>> exclusive cpusets scenarios which I don't thing anybody deploys with EAS?
>
> I am also wondering if the check for SD's CPUs could be removed...
Still not 100% sure here. I would have to play with cpusets and EAS a
little bit more. Are you thinking that in those cases p->cpus_ptr
already covers the cpuset restriction so that the sd mask isn't necessary?
next prev parent reply other threads:[~2025-08-15 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 9:33 Xuewen Yan
2025-08-12 21:29 ` Christian Loehle
2025-08-14 8:46 ` Dietmar Eggemann
2025-08-14 9:52 ` Xuewen Yan
2025-08-15 13:01 ` Dietmar Eggemann [this message]
2025-08-18 11:05 ` Xuewen Yan
2025-08-18 15:24 ` Dietmar Eggemann
2025-08-19 2:02 ` Xuewen Yan
2025-08-19 14:01 ` Dietmar Eggemann
2025-08-20 11:09 ` Xuewen Yan
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=8a84e658-1c2d-4380-8979-e1cc5bf5768d@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=bsegall@google.com \
--cc=christian.loehle@arm.com \
--cc=juri.lelli@redhat.com \
--cc=ke.wang@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vdonnefort@google.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=xuewen.yan94@gmail.com \
--cc=xuewen.yan@unisoc.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®