From: Pierre Gondois <pierre.gondois@arm.com>
To: "Zhang, Rui" <rui.zhang@intel.com>, "Lu, Aaron" <aaron.lu@intel.com>
Cc: "tj@kernel.org" <tj@kernel.org>,
"dietmar.eggemann@arm.com" <dietmar.eggemann@arm.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
"longman@redhat.com" <longman@redhat.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
Subject: Re: [PATCH] sched/fair: Skip cpus with no sched domain attached during NOHZ idle balance
Date: Fri, 22 Sep 2023 17:03:37 +0200 [thread overview]
Message-ID: <2a3c2cf0-44e3-befd-c7b5-d3c1fafbf2cd@arm.com> (raw)
In-Reply-To: <0a0ff05cd1ef629cfa0a4c9392f499459fe814e7.camel@intel.com>
Hi Rui,
On 9/20/23 09:24, Zhang, Rui wrote:
> Hi, Pierre,
>
> Sorry for the late response. I'm still ramping up on the related code.
No worries, I also need to read the code,
>
> On Thu, 2023-09-14 at 16:53 +0200, Pierre Gondois wrote:
>>
>>
>> On 9/14/23 11:23, Zhang, Rui wrote:
>>> Hi, Pierre,
>>>
>>>>
>>>> Yes right indeed,
>>>> This happens when putting a CPU offline (as you mentioned
>>>> earlier,
>>>> putting a CPU offline clears the CPU in the idle_cpus_mask).
>>>>
>>>> The load balancing related variables
>>>
>>> including?
>>
>> I meant the nohz idle variables in the load balancing, so I was
>> referring to:
>> (struct sched_domain_shared).nr_busy_cpus
>> (struct sched_domain).nohz_idle
>> nohz.idle_cpus_mask
>> nohz.nr_cpus
>> (struct rq).nohz_tick_stopped
>
> IMO, the problem is that, for an isolated CPU,
> 1. it is not an idle cpu (nohz.idle_cpus_mask should be cleared)
> 2. it is not a busy cpu (sds->nr_busy_cpus should be decreased)
>
> But current code does not have a third state to describe this, so we
> need to either
> 1. add extra logic, like on_null_domain() checks
I m not sure I understand, do you mean adding on_null_domain() in addition
to the one in the present patch ?
> or
> 2. rely on current logic, but update all related variables correctly,
> like you proposed.
>
> But in any case, we should stick with one direction.
>
> If we follow the first one, the original patch should be used, which
> IMO is simple and straight forward.
> If we follow the later one, we'd better audit and remove the current
> on_null_domain() usage at the same time. TBH, I'm not confident enough
Here aswell, I'm not sure I understand whether you are referring to
the on_null_domain() call in the present patch or to the on_null_domain()
calls in fair.c ?
Regards,
Pierre
> to make such a change. But if you want to propose something, I'd glad
> to test it.
>
> thanks,
> rui
>
next prev parent reply other threads:[~2023-09-22 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 9:08 Zhang Rui
2023-08-09 7:00 ` Chen Yu
2023-08-11 8:49 ` Zhang, Rui
2023-08-14 3:14 ` Aaron Lu
2023-08-14 8:30 ` Zhang, Rui
2023-09-08 9:43 ` Pierre Gondois
2023-09-11 11:42 ` Aaron Lu
2023-09-11 16:23 ` Zhang, Rui
2023-09-12 14:32 ` Pierre Gondois
2023-09-14 9:23 ` Zhang, Rui
2023-09-14 14:53 ` Pierre Gondois
2023-09-20 7:24 ` Zhang, Rui
2023-09-22 15:03 ` Pierre Gondois [this message]
2023-11-15 20:01 ` Vincent Guittot
2023-11-16 7:31 ` Zhang, Rui
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=2a3c2cf0-44e3-befd-c7b5-d3c1fafbf2cd@arm.com \
--to=pierre.gondois@arm.com \
--cc=aaron.lu@intel.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@intel.com \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.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®