From: Shrikanth Hegde <sshegde@linux.vnet.ibm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>,
Ingo Molnar <mingo@kernel.org>
Cc: peterz@infradead.org, dietmar.eggemann@arm.com,
linux-kernel@vger.kernel.org, srikar@linux.vnet.ibm.com,
yu.c.chen@intel.com, tim.c.chen@linux.intel.com
Subject: Re: [PATCH] sched: move access of avg_rt and avg_dl into existing helper functions
Date: Fri, 22 Dec 2023 13:32:26 +0530 [thread overview]
Message-ID: <e265378b-f81b-4c4c-9192-b383340c9be0@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAKfTPtBYRT9oOoLwZ-Gg3KVdK+2iJnPaXaWfiuebnGEOOArH0Q@mail.gmail.com>
On 12/21/23 9:46 PM, Vincent Guittot wrote:
> Hi Shrikanth,
>
> On Wed, 20 Dec 2023 at 15:49, Shrikanth Hegde
> <sshegde@linux.vnet.ibm.com> wrote:
>>
>>
>>
>> On 12/20/23 7:29 PM, Vincent Guittot wrote:
>>
>> Hi Vincent, thanks for taking a look.
>>
>>> On Wed, 20 Dec 2023 at 07:55, Shrikanth Hegde
>>> <sshegde@linux.vnet.ibm.com> wrote:
>>>>
>
> [...]
>
>>>> -#ifdef CONFIG_HAVE_SCHED_AVG_IRQ
>>>> - if (READ_ONCE(rq->avg_irq.util_avg))
>>>> + if (cpu_util_irq(rq))
>>>
>>> cpu_util_irq doesn't call READ_ONCE()
>>>
>>
>>
>> I see. Actually it would be right if cpu_util_irq does call READ_ONCE no?
>
> Yes, cpu_util_irq should call READ_ONCE()
>
Ok.
Sorry I forgot to mention about avg_irq.
I will send out v2 with the above change of READ_ONCE added soon.
>>
>> Sorry i havent yet understood the memory barriers in details. Please correct me
>> if i am wrong here,
>> since ___update_load_avg(&rq->avg_irq, 1) does use WRITE_ONCE and reading out this
>> value using cpu_util_irq on a different CPU should use READ_ONCE no?
>
> Yes
>
>>
>>>
>>>> return true;
>>>> -#endif
>>>>
>>>> return false;
>>>> }
>>>> @@ -9481,8 +9479,8 @@ static unsigned long scale_rt_capacity(int cpu)
>>>> * avg_thermal.load_avg tracks thermal pressure and the weighted
>>>> * average uses the actual delta max capacity(load).
>>>> */
>>>> - used = READ_ONCE(rq->avg_rt.util_avg);
>>>> - used += READ_ONCE(rq->avg_dl.util_avg);
>>>> + used = cpu_util_rt(rq);
>>>> + used += cpu_util_dl(rq);
>>>> used += thermal_load_avg(rq);
>>>>
>>>> if (unlikely(used >= max))
>>>> --
>>>> 2.39.3
>>>>
next prev parent reply other threads:[~2023-12-22 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 6:55 Shrikanth Hegde
2023-12-20 10:11 ` [tip: sched/core] sched/fair: Use existing helper functions to access ->avg_rt and ->avg_dl tip-bot2 for Shrikanth Hegde
2023-12-20 13:59 ` [PATCH] sched: move access of avg_rt and avg_dl into existing helper functions Vincent Guittot
2023-12-20 14:48 ` Shrikanth Hegde
2023-12-21 16:16 ` Vincent Guittot
2023-12-22 8:02 ` Shrikanth Hegde [this message]
2023-12-20 19:53 ` Ingo Molnar
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=e265378b-f81b-4c4c-9192-b383340c9be0@linux.vnet.ibm.com \
--to=sshegde@linux.vnet.ibm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=yu.c.chen@intel.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®