mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Qais Yousef <qyousef@layalina.io>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	Valentin Schneider <vschneid@redhat.com>,
	Christian Loehle <christian.loehle@arm.com>,
	Hongyan Xia <hongyan.xia2@arm.com>,
	John Stultz <jstultz@google.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] sched: Consolidate cpufreq updates
Date: Sat, 27 Jul 2024 10:15:26 +0200	[thread overview]
Message-ID: <962a0fe6-c6bf-415a-9c57-ecb259bd0066@arm.com> (raw)
In-Reply-To: <20240724211012.mxb6vgbhurk7rcvc@airbuntu>

On 24/07/2024 23:10, Qais Yousef wrote:
> On 07/05/24 13:50, Dietmar Eggemann wrote:

[...]

>> I tried to explained it in the 4 lines below. With a local 'decayed'
>> update_cfs_rq_load_avg() and propagate_entity_load_avg() set it every
>> time update_load_avg() gets called. And this then determines whether
>> update_tg_load_avg() is called on this cfs_rq later in update_load_avg().
>>
>> The new code:
>>
>>   cfs_rq->decayed |= update_cfs_rq_load_avg() (*)
>>   cfs_rq->decayed |= propagate_entity_load_avg()
>>
>> will not reset 'cfs_rq->decayed' for non-root cfs_rq's.
>>
>> (*) You changed this in v3 from:
>>
>>   cfs_rq->decayed  = update_cfs_rq_load_avg()
>>
>>
>>>> update_load_avg() itself. They will stay decayed after cfs_rq->decayed
>>>> has been set to 1 once and will never be reset to 0. So with UPDATE_TG
>>>> update_tg_load_avg() will then always be called on those non-root
>>>> cfs_rq's all the time.
>>>
>>> We could add a check to update only the root cfs_rq. But what do we gain? Or
>>> IOW, what is the harm of unconditionally updating cfs_rq->decayed given that we
>>> only care about the root cfs_rq? I see more if conditions and branches which
>>> I am trying to avoid.
>>
>> Yes, keep 'decayed' local and add a:
>>
>>     if (cfs_rq == &rq_of(cfs_rq)->cfs)
>>         cfs_rq->decayed = decayed
> 
> I still don't see a problem here. If we don't do it this way, how the outcome
> of frequency selection will change? You're replacing set-but-not-cleared with
> never-set, and un unconditional write with a branch.

This seems to be a misunderstanding. The problem is not with the
frequency selection.

The issue I see is when you set 'cfs_rq->decayed' for a non-root cfs_rq
it stays set forever since there is no code to reset it. This leads to
the fact that update_tg_load_avg(..., UPDATE_TG) is then always called
for this cfs_rq within update_load_avg() whereas before 'decayed' was
evaluated with each invocation of update_load_avg().

[...]













  reply	other threads:[~2024-07-27  8:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 20:14 Qais Yousef
2024-06-25 12:58 ` Dietmar Eggemann
2024-06-28  1:52   ` Qais Yousef
2024-07-04 10:12     ` Dietmar Eggemann
2024-07-05  0:22       ` Qais Yousef
2024-07-05 11:50         ` Dietmar Eggemann
2024-07-09  7:49           ` Vincent Guittot
2024-07-24 21:10           ` Qais Yousef
2024-07-27  8:15             ` Dietmar Eggemann [this message]
2024-07-28 19:29               ` Qais Yousef
2024-07-09  7:48 ` Vincent Guittot
2024-07-10 16:22   ` Dietmar Eggemann
2024-07-24 21:22   ` Qais Yousef

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=962a0fe6-c6bf-415a-9c57-ecb259bd0066@arm.com \
    --to=dietmar.eggemann@arm.com \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=christian.loehle@arm.com \
    --cc=hongyan.xia2@arm.com \
    --cc=jstultz@google.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=qyousef@layalina.io \
    --cc=rafael@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@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®