From: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>
Cc: Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Adam Li <adamli@os.amperecomputing.com>,
Madadi Vineeth Reddy <vineethr@linux.ibm.com>
Subject: Re: [PATCH] sched/fair: Remove stale references to LAST_BUDDY and SKIP_BUDDY
Date: Sun, 13 Apr 2025 09:40:44 +0530 [thread overview]
Message-ID: <4da6d43b-59f6-48e4-b58c-2f0792035851@linux.ibm.com> (raw)
In-Reply-To: <20250314090128.25141-1-vineethr@linux.ibm.com>
Hi Peter, Ingo,
Ping.
Any thoughts on this? Can it be picked up?
Thanks,
Madadi Vineeth Reddy
On 14/03/25 14:31, Madadi Vineeth Reddy wrote:
> Commit 5e963f2bd465 ("sched/fair: Commit to EEVDF") removed the
> functionality associated with LAST_BUDDY and SKIP_BUDDY. However,
> some outdated references remained in the comments for pick_next_entity
> and check_preempt_wakeup_fair. This commit cleans up those comments
> to maintain clarity and correctness.
>
> No functional change intended.
>
> Co-developed-by: Adam Li <adamli@os.amperecomputing.com>
> Signed-off-by: Adam Li <adamli@os.amperecomputing.com>
> Signed-off-by: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
> ---
> kernel/sched/fair.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 9dafb374d76d..379dbcbb24e9 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -5578,8 +5578,6 @@ static int dequeue_entities(struct rq *rq, struct sched_entity *se, int flags);
> * Pick the next process, keeping these things in mind, in this order:
> * 1) keep things fair between processes/task groups
> * 2) pick the "next" process, since someone really wants that to run
> - * 3) pick the "last" process, for cache locality
> - * 4) do not run the "skip" process, if something else is available
> */
> static struct sched_entity *
> pick_next_entity(struct rq *rq, struct cfs_rq *cfs_rq)
> @@ -8780,9 +8778,7 @@ static void check_preempt_wakeup_fair(struct rq *rq, struct task_struct *p, int
> *
> * Note: this also catches the edge-case of curr being in a throttled
> * group (e.g. via set_curr_task), since update_curr() (in the
> - * enqueue of curr) will have resulted in resched being set. This
> - * prevents us from potentially nominating it as a false LAST_BUDDY
> - * below.
> + * enqueue of curr) will have resulted in resched being set.
> */
> if (test_tsk_need_resched(rq->curr))
> return;
next prev parent reply other threads:[~2025-04-13 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 9:01 Madadi Vineeth Reddy
2025-04-13 4:10 ` Madadi Vineeth Reddy [this message]
2025-08-07 6:37 ` Madadi Vineeth Reddy
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=4da6d43b-59f6-48e4-b58c-2f0792035851@linux.ibm.com \
--to=vineethr@linux.ibm.com \
--cc=20250314090128.25141-1-vineethr@linux.ibm.com \
--cc=adamli@os.amperecomputing.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@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®