[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6fcef844-f406-47cd-81b1-9624976a052f@amd.com>
Date: Thu, 22 Jan 2026 08:21:09 +0530
From: K Prateek Nayak <kprateek.nayak@....com>
To: Shrikanth Hegde <sshegde@...ux.ibm.com>
CC: Ingo Molnar <mingo@...hat.com>, Peter Zijlstra <peterz@...radead.org>,
Juri Lelli <juri.lelli@...hat.com>, Vincent Guittot
<vincent.guittot@...aro.org>, <linux-kernel@...r.kernel.org>, "Dietmar
Eggemann" <dietmar.eggemann@....com>, Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>, "Valentin
Schneider" <vschneid@...hat.com>, Chen Yu <yu.c.chen@...el.com>, "Gautham R.
Shenoy" <gautham.shenoy@....com>
Subject: Re: [PATCH v3 1/8] sched/topology: Compute sd_weight considering
cpuset partitions
Hello Shrikanth,
On 1/21/2026 9:12 PM, Shrikanth Hegde wrote:
>
>
> On 1/20/26 5:02 PM, K Prateek Nayak wrote:
>> The "sd_weight" used for calculating the load balancing interval, and
>> its limits, considers the span weight of the entire topology level
>> without accounting for cpuset partitions.
>>
>
> Please add one example showing the wrong sd_weights
> while having cpuset partitions. That would be helpful.
Ack! I'll update with an example in the next version.
>
>> Compute the "sd_weight" after computing the "sd_span" considering the
>> cpu_map covered by the partition, and set the load balancing interval,
>> and its limits accordingly.
>>
>> Fixes: cb83b629bae03 ("sched/numa: Rewrite the CONFIG_NUMA sched domain support")
>> Signed-off-by: K Prateek Nayak <kprateek.nayak@....com>
>> ---
>> Changelog rfc v2..v3:
>>
>> o New patch.
>> ---
>
> Reviewed-by: Shrikanth Hegde <sshegde@...ux.ibm.com>
Thanks a ton for the review.
--
Thanks and Regards,
Prateek
Powered by blists - more mailing lists