From: Chuyi Zhou <zhouchuyi@bytedance.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
vschneid@redhat.com, longman@redhat.com, riel@surriel.com,
chengming.zhou@linux.dev, kprateek.nayak@amd.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Take the scheduling domain into account in numa balancin
Date: Tue, 7 Jan 2025 21:03:43 +0800 [thread overview]
Message-ID: <17c4b89f-8585-47f8-837d-907b30002f22@bytedance.com> (raw)
In-Reply-To: <20250107104824.GL20870@noisy.programming.kicks-ass.net>
在 2025/1/7 18:48, Peter Zijlstra 写道:
> On Fri, Jan 03, 2025 at 08:40:18PM +0800, Chuyi Zhou wrote:
>> Hello Peter,
>>
>> 在 2025/1/3 19:36, Peter Zijlstra 写道:
>>> Your $subject and actual patches do not patch.
>>>
>>> Your subject suggests you're taking the scheduling domains into account
>>> for numa balancing, your actual patches are bunch of special case hacks
>>> that totally ignore the actual sched domains
>>
>> The subject is indeed inappropriate, but the issues mentioned in this
>> patchset still exist, right?
>>
>> - We should not consider isolated CPUs in numa_stats.
>> - We should not select isolated CPUs as candidate CPUs.
>>
>> The current patch handle the above cases with hacks because I thought this
>> kind of change is minimal to fix this issue. Perhaps you have a better
>> solution for this issue? If so, please let me know, and I am more than
>> willing to continue addressing this problem.
>
> I would much rather see you do what the subject claims :-)
>
> At the very least you should mask the whole thing against rq->rd->span
> if there is a rq->rd at all ofcourse. This is not just the iteration in
> update_numa_stats() but also the for_each_node_state() iteration.
>
> I'm not sure there's anything saner than:
>
> cpumask_intersects(rq->rd->span, cpumask_of_node(nid))
>
Thank you for your suggestion. It will be implemented in the next version.
Thansk.
prev parent reply other threads:[~2025-01-07 13:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 6:59 Chuyi Zhou
2025-01-03 6:59 ` [PATCH v2 1/3] sched/fair: Remove unused task_numa_migrate return value Chuyi Zhou
2025-01-05 18:28 ` Madadi Vineeth Reddy
2025-01-03 6:59 ` [PATCH v2 2/3] sched/fair: Ignore isolated cpus in update_numa_stat Chuyi Zhou
2025-01-05 18:52 ` Madadi Vineeth Reddy
2025-01-07 13:16 ` Chuyi Zhou
2025-01-07 18:30 ` Madadi Vineeth Reddy
2025-01-07 18:39 ` Waiman Long
2025-01-08 10:47 ` Chuyi Zhou
2025-01-03 6:59 ` [PATCH v2 3/3] sched/fair: Ensure select housekeeping cpus in task_numa_find_cpu Chuyi Zhou
2025-01-03 11:36 ` [PATCH v2 0/3] Take the scheduling domain into account in numa balancin Peter Zijlstra
2025-01-03 12:40 ` Chuyi Zhou
2025-01-07 10:48 ` Peter Zijlstra
2025-01-07 13:03 ` Chuyi Zhou [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=17c4b89f-8585-47f8-837d-907b30002f22@bytedance.com \
--to=zhouchuyi@bytedance.com \
--cc=bsegall@google.com \
--cc=chengming.zhou@linux.dev \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®