From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Chuyi Zhou <zhouchuyi@bytedance.com>, <mingo@redhat.com>,
<peterz@infradead.org>, <juri.lelli@redhat.com>,
<vincent.guittot@linaro.org>
Cc: <chengming.zhou@linux.dev>, <linux-kernel@vger.kernel.org>,
Vishal Chourasia <vishalc@linux.ibm.com>
Subject: Re: [PATCH v2] sched/fair: Remove cfs_rq::nr_spread_over and cfs_rq::exec_clock
Date: Thu, 18 Jul 2024 08:58:48 +0530 [thread overview]
Message-ID: <3a2efbd7-075c-2a93-0ea7-51566362f17e@amd.com> (raw)
In-Reply-To: <20240717143342.593262-1-zhouchuyi@bytedance.com>
Hello Chuyi,
On 7/17/2024 8:03 PM, Chuyi Zhou wrote:
> 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
scripts/checkpatch.pl complains about the commit description style here.
The above can be reworded as:
Commit 5e963f2bd465 ("sched/fair: Commit to EEVDF") removed its usage.
>
> 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
And this as:
Commit 5d69eca542ee ("sched: Unify runtime accounting across classes")
removed its usage.
>
> cfs_rq::nr_spread_over and cfs_rq::exec_clock are not used anymore in
> eevdf. Remove them from struct cfs_rq.
>
> Signed-off-by: Chuyi Zhou <zhouchuyi@bytedance.com>
> Acked-by: Vishal Chourasia <vishalc@linux.ibm.com>
> Reviewed-by: Chengming Zhou <chengming.zhou@linux.dev>
Apart from those nits,
Reviewed-by: K Prateek Nayak <kprateek.nayak@amd.com>
--
Thanks and Regards,
Prateek
> ---
> kernel/sched/debug.c | 4 ----
> kernel/sched/sched.h | 6 ------
> 2 files changed, 10 deletions(-)
>
> [..snip..]
next prev parent reply other threads:[~2024-07-18 3:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 14:33 Chuyi Zhou
2024-07-18 3:28 ` K Prateek Nayak [this message]
2024-07-18 8:20 ` Chuyi Zhou
2024-07-29 10:34 ` [tip: sched/core] " tip-bot2 for Chuyi Zhou
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=3a2efbd7-075c-2a93-0ea7-51566362f17e@amd.com \
--to=kprateek.nayak@amd.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 \
--cc=zhouchuyi@bytedance.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®