From: Chuyi Zhou <zhouchuyi@bytedance.com>
To: Chengming Zhou <chengming.zhou@linux.dev>,
Vishal Chourasia <vishalc@linux.ibm.com>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/fair: Remove cfs_rq::nr_spread_over and cfs_rq::exec_clock
Date: Wed, 17 Jul 2024 20:37:19 +0800 [thread overview]
Message-ID: <866f9ea0-b472-41eb-b5d3-59c0894b6fa6@bytedance.com> (raw)
In-Reply-To: <9b0b69bf-dac0-457d-a4dc-4bea18eecc43@linux.dev>
在 2024/7/17 19:25, Chengming Zhou 写道:
> On 2024/7/17 19:07, Vishal Chourasia wrote:
>> On Tue, Jul 16, 2024 at 11:06:34PM +0800, Chuyi Zhou wrote:
>>> cfs_rq::nr_spread_over and cfs_rq::exec_clock are not used anymore in
>>> eevdf. Remove them from struct cfs_rq.
>>>
>>
>> nr_spread_over tracks the number of instances where the difference
>> between a scheduling entity's virtual runtime and the minimum virtual
>> runtime in the runqueue exceeds three times the scheduler latency,
>> indicating significant disparity in task scheduling.
>> Commit that removed its usage: 5e963f2bd: sched/fair: Commit to EEVDF
>>
>>
>> cfs_rq->exec_clock was used to account for time spent executing tasks.
>> Commit that removed its usage: 5d69eca542ee1 sched: Unify runtime
>> accounting across classes
>>
>>> Signed-off-by: Chuyi Zhou <zhouchuyi@bytedance.com>
>>
>> Acked-by: Vishal Chourasia <vishalc@linux.ibm.com>
>
> Looks good to me! Maybe it's better to add these to your changelog.
>
> Reviewed-by: Chengming Zhou <chengming.zhou@linux.dev>
>
> Thanks.
Thanks, will do this later.
prev parent reply other threads:[~2024-07-17 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 15:06 Chuyi Zhou
2024-07-17 11:07 ` Vishal Chourasia
2024-07-17 11:25 ` Chengming Zhou
2024-07-17 12:37 ` 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=866f9ea0-b472-41eb-b5d3-59c0894b6fa6@bytedance.com \
--to=zhouchuyi@bytedance.com \
--cc=chengming.zhou@linux.dev \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=vishalc@linux.ibm.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®