public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriele Monaco <gmonaco@redhat.com>
To: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	 Ingo Molnar <mingo@redhat.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH v12 0/3] sched: Restructure task_mm_cid_work for predictability
Date: Wed, 09 Apr 2025 11:45:35 +0200	[thread overview]
Message-ID: <fde0a08192f4e0d51d2e9e234d3612de6311cb79.camel@redhat.com> (raw)
In-Reply-To: <89bc1d11-c2bc-43d7-9a22-e159175706cc@efficios.com>

On Wed, 2025-03-26 at 10:33 -0400, Mathieu Desnoyers wrote:
> On 2025-03-26 03:31, Gabriele Monaco wrote:
> > On Tue, 2025-03-11 at 07:28 +0100, Gabriele Monaco wrote:
> > > This patchset moves the task_mm_cid_work to a preemptible and
> > > migratable
> > > context. This reduces the impact of this work to the scheduling
> > > latency
> > > of real time tasks.
> > > The change makes the recurrence of the task a bit more
> > > predictable.
> > > 
> > 
> > The series was review and, in my opinion, is ready for inclusion.
> > Peter, Ingo, can we merge it?
> 
> I agree. I've reviewed the entire series a few weeks ago and it
> looks good to me.
> 

Gentle reminder. Peter, Ingo can we merge this?

Thanks,
Gabriele


      reply	other threads:[~2025-04-09  9:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11  6:28 [PATCH v12 0/3] sched: Restructure task_mm_cid_work for predictability Gabriele Monaco
2025-03-11  6:28 ` [PATCH v12 1/3] sched: Add prev_sum_exec_runtime support for RT, DL and SCX classes Gabriele Monaco
2025-03-11  6:28 ` [PATCH v12 2/3] sched: Move task_mm_cid_work to mm work_struct Gabriele Monaco
2025-04-09 14:03   ` Peter Zijlstra
2025-04-09 14:15     ` Mathieu Desnoyers
2025-04-09 15:20       ` Peter Zijlstra
2025-04-09 15:53         ` Mathieu Desnoyers
2025-04-09 19:08           ` Peter Zijlstra
2025-04-10 12:50           ` [PATCH] fixup: " Gabriele Monaco
2025-04-10 14:04             ` Mathieu Desnoyers
2025-04-10 14:36               ` Gabriele Monaco
2025-03-11  6:28 ` [PATCH v12 3/3] selftests/rseq: Add test for mm_cid compaction Gabriele Monaco
2025-03-26  7:31 ` [PATCH v12 0/3] sched: Restructure task_mm_cid_work for predictability Gabriele Monaco
2025-03-26 14:33   ` Mathieu Desnoyers
2025-04-09  9:45     ` Gabriele Monaco [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=fde0a08192f4e0d51d2e9e234d3612de6311cb79.camel@redhat.com \
    --to=gmonaco@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@redhat.org \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=shuah@kernel.org \
    /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