From: Steven Rostedt <rostedt@goodmis.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Joel Fernandes <joelagnelf@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v3] tracing: Guard __DECLARE_TRACE() use of __DO_TRACE_CALL() with SRCU-fast
Date: Sat, 13 Dec 2025 01:20:50 -0500 [thread overview]
Message-ID: <20251213012050.576eead3@fedora> (raw)
In-Reply-To: <09c76498-6a0b-4880-8a86-2a295c47c703@efficios.com>
On Fri, 12 Dec 2025 23:19:41 -0500
Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> Here is one additional thing to keep in mind: although
> SRCU-fast is probably quite fast (as the name implies),
> last time I tried using migrate disable in a fast path
> I was surprised to see verbosity of the generated assembly,
> and how slow it was compared to preempt disable.
>
> So before using migrate disable on a fast path, at least on
> non-preempt-RT configs, we should carefully consider the
> performance impact of migrate disable.
Right, which is another reason I'm keeping that part of the patch as-is.
-- Steve
next prev parent reply other threads:[~2025-12-13 6:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 4:20 [PATCH v3] tracing: Guard __DECLARE_TRACE() use of __DO_TRACE_CALL() with SRCU-fast Paul E. McKenney
2025-12-08 9:43 ` Steven Rostedt
2025-12-08 20:46 ` Paul E. McKenney
2025-12-09 0:38 ` Steven Rostedt
2025-12-09 22:29 ` Paul E. McKenney
2025-12-10 3:11 ` Steven Rostedt
2025-12-11 20:02 ` Joel Fernandes
2025-12-11 20:23 ` Paul E. McKenney
2025-12-12 0:12 ` Joel Fernandes
2025-12-12 0:47 ` Paul E. McKenney
2025-12-12 3:43 ` Joel Fernandes
2025-12-12 7:50 ` Paul E. McKenney
2025-12-12 9:28 ` Joel Fernandes
2025-12-12 23:10 ` Paul E. McKenney
2025-12-12 23:54 ` Joel Fernandes
2025-12-13 0:06 ` Paul E. McKenney
2025-12-13 2:18 ` Steven Rostedt
2025-12-13 4:19 ` Mathieu Desnoyers
2025-12-13 6:20 ` Steven Rostedt [this message]
2025-12-12 1:13 ` Steven Rostedt
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=20251213012050.576eead3@fedora \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=bpf@vger.kernel.org \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=tglx@linutronix.de \
/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