All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Yuri Andriaccio <yurand2000@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	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>,
	linux-kernel@vger.kernel.org,
	Luca Abeni <luca.abeni@santannapisa.it>,
	Yuri Andriaccio <yuri.andriaccio@santannapisa.it>
Subject: Re: [RFC PATCH v5 14/29] sched/rt: Update task event callbacks for HCBS scheduling
Date: Tue, 5 May 2026 15:16:28 +0200	[thread overview]
Message-ID: <20260505131628.GN1026330@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260430213835.62217-15-yurand2000@gmail.com>

On Thu, Apr 30, 2026 at 11:38:18PM +0200, Yuri Andriaccio wrote:
> diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
> index defb812b0e48..67fbf4bbe461 100644
> --- a/kernel/sched/rt.c
> +++ b/kernel/sched/rt.c
> @@ -975,7 +975,58 @@ static int balance_rt(struct rq *rq, struct task_struct *p, struct rq_flags *rf)
>  static void wakeup_preempt_rt(struct rq *rq, struct task_struct *p, int flags)
>  {
>  	struct task_struct *donor = rq->donor;
> +	struct sched_dl_entity *woken_dl_se = NULL;
> +	struct sched_dl_entity *donor_dl_se = NULL;
> +
> +	if (!rt_group_sched_enabled())
> +		goto no_group_sched;
> 
> +	/*
> +	 * Preemption checks are different if the waking task and the current task
> +	 * are running on the global runqueue or in a cgroup. The following rules
> +	 * apply:
> +	 *   - dl-tasks (and equally dl_servers) always preempt FIFO/RR tasks.
> +	 *     - if curr is a FIFO/RR task inside a cgroup (i.e. run by a
> +	 *       dl_server), or curr is a DEADLINE task and waking is a FIFO/RR task
> +	 *       on the root cgroup, do nothing.
> +	 *     - if waking is inside a cgroup but curr is a FIFO/RR task in the root
> +	 *       cgroup, always reschedule.
> +	 *   - if they are both on the global runqueue, run the standard code.
> +	 *   - if they are both in the same cgroup, check for tasks priorities.
> +	 *   - if they are both in a cgroup, but not the same one, check whether the
> +	 *     woken task's dl_server preempts the current's dl_server.
> +	 *   - if curr is a DEADLINE task and waking is in a cgroup, check whether
> +	 *     the woken task's server preempts curr.
> +	 */
> +	if (is_dl_group(rt_rq_of_se(&p->rt)))
> +		woken_dl_se = dl_group_of(rt_rq_of_se(&p->rt));
> +	if (is_dl_group(rt_rq_of_se(&donor->rt)))
> +		donor_dl_se = dl_group_of(rt_rq_of_se(&donor->rt));
> +	else if (task_has_dl_policy(donor))
> +		donor_dl_se = &donor->dl;
> +
> +	if (woken_dl_se != NULL && donor_dl_se != NULL) {
> +		if (woken_dl_se == donor_dl_se) {
> +			if (p->prio < donor->prio)
> +				resched_curr(rq);
> +
> +			return;

This is effectively the traditional test, why not goto no_group_sched at
this point and share that code rather than duplicate?

> +		}
> +
> +		if (dl_entity_preempt(woken_dl_se, donor_dl_se))
> +			resched_curr(rq);
> +
> +		return;
> +
> +	} else if (woken_dl_se != NULL) {
> +		resched_curr(rq);
> +		return;
> +
> +	} else if (donor_dl_se != NULL) {
> +		return;
> +	}
> +
> +no_group_sched:
>  	/*
>  	 * XXX If we're preempted by DL, queue a push?
>  	 */

  parent reply	other threads:[~2026-05-05 13:16 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260430213835.62217-1-yurand2000@gmail.com>
     [not found] ` <20260430213835.62217-14-yurand2000@gmail.com>
2026-05-05 13:04   ` [RFC PATCH v5 13/29] sched/rt: Implement dl-server operations for rt-cgroups Peter Zijlstra
     [not found] ` <20260430213835.62217-15-yurand2000@gmail.com>
2026-05-05 13:16   ` Peter Zijlstra [this message]
     [not found] ` <20260430213835.62217-16-yurand2000@gmail.com>
2026-05-05 14:36   ` [RFC PATCH v5 15/29] sched/rt: Update rt-cgroup schedulability checks Peter Zijlstra
     [not found] ` <20260430213835.62217-19-yurand2000@gmail.com>
2026-05-05 14:59   ` [RFC PATCH v5 18/29] sched/core: Cgroup v2 support Peter Zijlstra
2026-05-06 19:58     ` luca abeni
2026-05-07  7:01       ` Peter Zijlstra
2026-05-07 13:30         ` luca abeni
2026-05-07 14:16           ` Peter Zijlstra
     [not found] ` <20260430213835.62217-20-yurand2000@gmail.com>
2026-05-05 15:01   ` [RFC PATCH v5 19/29] sched/rt: Remove support for cgroups-v1 Peter Zijlstra
2026-05-07 15:35     ` Juri Lelli
2026-05-13 12:15       ` Yuri Andriaccio
2026-05-13 14:37         ` Juri Lelli
     [not found] ` <20260430213835.62217-21-yurand2000@gmail.com>
2026-05-05 15:15   ` [RFC PATCH v5 20/29] sched/deadline: Allow deeper hierarchies of RT cgroups Peter Zijlstra
2026-05-05 19:56     ` Tejun Heo
2026-05-07 10:53       ` Peter Zijlstra
2026-05-07 15:03         ` Juri Lelli
2026-05-07 15:05           ` Peter Zijlstra
2026-05-07 16:39           ` luca abeni
2026-05-11  9:29             ` Juri Lelli
2026-05-11 17:52               ` Tejun Heo
2026-05-07 16:44         ` luca abeni
2026-05-11  9:40         ` luca abeni
2026-05-11 18:15           ` Tejun Heo
2026-05-11 17:37         ` Tejun Heo
2026-05-07 14:30       ` luca abeni
2026-05-11 18:28         ` Tejun Heo
2026-05-12 17:38           ` Yuri Andriaccio
2026-05-12 18:19             ` Tejun Heo
2026-05-12 18:20               ` Tejun Heo
2026-05-13 12:08                 ` Yuri Andriaccio
2026-05-13 19:10                   ` Tejun Heo
2026-05-14  7:25               ` luca abeni
2026-05-14 22:20                 ` Tejun Heo
     [not found] ` <20260430213835.62217-23-yurand2000@gmail.com>
2026-05-05 15:20   ` [RFC PATCH v5 22/29] sched/rt: Add rt-cgroup migration functions Peter Zijlstra
2026-05-05 15:24   ` Peter Zijlstra

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=20260505131628.GN1026330@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.abeni@santannapisa.it \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=yurand2000@gmail.com \
    --cc=yuri.andriaccio@santannapisa.it \
    /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.