From: Matt Fleming <matt@readmodwrite.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Joel Fernandes <joelagnelf@nvidia.com>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>, Tejun Heo <tj@kernel.org>,
Andrea Righi <arighi@nvidia.com>,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
sched-ext@lists.linux.dev, stable@vger.kernel.org,
kernel-team@cloudflare.com,
Matt Fleming <mfleming@cloudflare.com>
Subject: Re: [PATCH] rcu-tasks: Defer IRQ-disabled callback enqueue to irq_work
Date: Thu, 30 Jul 2026 13:19:11 +0100 [thread overview]
Message-ID: <amtBE9JlGBPwsIuU@matt-Precision-5490> (raw)
In-Reply-To: <6f002779-3607-47d8-af61-a74eeb987e6a@paulmck-laptop>
On Tue, Jul 28, 2026 at 11:44:04AM -0700, Paul E. McKenney wrote:
>
> Apologies for the delay!!!
No worries :)
> Alternatively, please do feel free to hold off until we get the public
> posting of the call_rcu() and call_srcu() deferral patch series.
> It will likely provide a helper function that you can use. To your
> credit, your initial definition of the irqsoff local variable within
> call_rcu_tasks_generic() is what we seem to be settling on. It should
> also clarify what needs to happen when a CPU goes offline with deferred
> callbacks.
Sure, I saw the patch series and will piggyback on top of it.
Thanks,
Matt
prev parent reply other threads:[~2026-07-30 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 10:12 Matt Fleming
2026-07-28 10:39 ` Matt Fleming
2026-07-28 18:44 ` Paul E. McKenney
2026-07-30 12:19 ` Matt Fleming [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=amtBE9JlGBPwsIuU@matt-Precision-5490 \
--to=matt@readmodwrite.com \
--cc=arighi@nvidia.com \
--cc=boqun@kernel.org \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=josh@joshtriplett.org \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mfleming@cloudflare.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sched-ext@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
--cc=urezki@gmail.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®