From: Breno Leitao <leitao@debian.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: rostedt@goodmis.org, pjaroszynski@nvidia.com,
Andrew Morton <akpm@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
puranjay@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
kernel-team@meta.com, dcostantino@meta.com
Subject: Re: [PATCH] mm/kmemleak: report RCU-tasks quiescent states during the scan
Date: Fri, 31 Jul 2026 11:07:44 -0700 [thread overview]
Message-ID: <amzjjjZrseO-jMJL@gmail.com> (raw)
In-Reply-To: <743bf971-b4aa-416b-b72b-88b538be727a@paulmck-laptop>
On Thu, Jul 30, 2026 at 07:57:22AM -0700, Paul E. McKenney wrote:
> > I suppose we want two things:
> >
> > 1) change cond_resched() with cond_resched_tasks_rcu_qs()
> > 2) Avoiding holding the ftrace lock while calling
> > synchronize_rcu_tasks()? It can take up to 10 minutes on a healthy
> > system to be releasd, right?
>
> I do very much like both of those options. ;-)
>
> If #2 is impossible, would it make sense to have a mutex_lock_idle() or
> similar in order to sanctify the lock synchronize_rcu_tasks() latencies?
How would mutex_lock_idle() differ from a regular mutex_lock() when
sanctifying synchronize_rcu_tasks() latencies?
next prev parent reply other threads:[~2026-07-31 18:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 13:23 [PATCH] mm/kmemleak: report RCU-tasks quiescent states during the scan Breno Leitao
2026-07-20 15:25 ` Paul E. McKenney
2026-07-20 22:39 ` Andrew Morton
2026-07-21 4:21 ` Paul E. McKenney
2026-07-23 13:26 ` Breno Leitao
2026-07-23 15:56 ` Paul E. McKenney
2026-07-24 9:58 ` Breno Leitao
2026-07-24 17:29 ` Paul E. McKenney
2026-07-27 13:04 ` Breno Leitao
2026-07-27 16:02 ` Breno Leitao
2026-07-30 14:06 ` Breno Leitao
2026-07-30 14:57 ` Paul E. McKenney
2026-07-31 18:07 ` Breno Leitao [this message]
2026-07-31 18:19 ` Paul E. McKenney
2026-07-21 0:00 ` SJ Park
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=amzjjjZrseO-jMJL@gmail.com \
--to=leitao@debian.org \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dcostantino@meta.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@kernel.org \
--cc=pjaroszynski@nvidia.com \
--cc=puranjay@kernel.org \
--cc=rostedt@goodmis.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