All of lore.kernel.org
 help / color / mirror / Atom feed
From: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
To: Zhongqiu Han <quic_zhonhan@quicinc.com>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
	rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
	vschneid@redhat.com, Adam Li <adamli@os.amperecomputing.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/fair: Update stale comments referencing last/skip buddy
Date: Thu, 7 Aug 2025 11:51:54 +0530	[thread overview]
Message-ID: <22e5bd44-1bba-4cc4-be21-04bbd9702da8@linux.ibm.com> (raw)
In-Reply-To: <20250805122316.1097085-1-quic_zhonhan@quicinc.com>

Hi Zhongqiu,

On 05/08/25 17:53, Zhongqiu Han wrote:
> Since the integration of EEVDF, the last/skip buddy scheduling features
> have been removed. This patch updates outdated comments that still
> reference these legacy behaviors to avoid inconsistencies.
> 
> Fixes: 5e963f2bd465 ("sched/fair: Commit to EEVDF")
> Signed-off-by: Zhongqiu Han <quic_zhonhan@quicinc.com>
> ---
>  kernel/sched/fair.c | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index b173a059315c..b3618aa075ec 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -5500,11 +5500,11 @@ set_next_entity(struct cfs_rq *cfs_rq, struct sched_entity *se)
>  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
> + * Pick the next sched_entity to run from cfs_rq.
> + *
> + * Prefer ->next buddy if sched_feat(PICK_BUDDY) is enabled and it's eligible,
> + * to improve cache locality.
> + * Otherwise, pick the entity via EEVDF for fairness and latency control.
>   */
>  static struct sched_entity *
>  pick_next_entity(struct rq *rq, struct cfs_rq *cfs_rq)
> @@ -8673,9 +8673,9 @@ 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. This
> +	 * prevents further preemption handling, including checks and potential
> +	 * reschedule triggering.
>  	 */
>  	if (test_tsk_need_resched(rq->curr))
>  		return;

Sent similar patch here https://lore.kernel.org/lkml/20250314090128.25141-1-vineethr@linux.ibm.com/
[PATCH] sched/fair: Remove stale references to LAST_BUDDY and SKIP_BUDDY

Thanks,
Madadi Vineeth Reddy

      reply	other threads:[~2025-08-07  6:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05 12:23 [PATCH] sched/fair: Update stale comments referencing last/skip buddy Zhongqiu Han
2025-08-07  6:21 ` Madadi Vineeth Reddy [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=22e5bd44-1bba-4cc4-be21-04bbd9702da8@linux.ibm.com \
    --to=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=quic_zhonhan@quicinc.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.