From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Joel Fernandes <joelagnelf@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>
Subject: Re: [PATCH v3] tracing: Guard __DECLARE_TRACE() use of __DO_TRACE_CALL() with SRCU-fast
Date: Thu, 11 Dec 2025 20:13:40 -0500 [thread overview]
Message-ID: <20251211201340.618195b2@fedora> (raw)
In-Reply-To: <febd477b-c111-4d5e-be89-cae3685853f5@paulmck-laptop>
On Thu, 11 Dec 2025 12:23:29 -0800
"Paul E. McKenney" <paulmck@kernel.org> wrote:
> > Is there a reason to not make non-RT also benefit from SRCU fast and trace points for BPF? Can be a follow up patch though if needed.
>
> Because in some cases the non-RT benefit is suspected to be negative
> due to increasing the probability of preemption in awkward places.
>
> > Reviewed-by: Joel Fernandes <joelagnelf@nvidia.com>
>
> Thank you, and I will let Steven collect this one.
>
Sure. Note, I'll be working on this next week.
-- Steve
prev parent reply other threads:[~2025-12-12 1:13 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
2025-12-12 1:13 ` Steven Rostedt [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=20251211201340.618195b2@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 \
/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.