From: "Paul E. McKenney" <paulmck@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Joel Fernandes <joel@joelfernandes.org>,
Network Development <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
rcu@vger.kernel.org, kernel-team <kernel-team@cloudflare.com>
Subject: Re: [PATCH] net: raise RCU qs after each threaded NAPI poll
Date: Thu, 7 Mar 2024 10:58:40 -0800 [thread overview]
Message-ID: <1165c893-b812-4f88-a1d6-fff85592657e@paulmck-laptop> (raw)
In-Reply-To: <20240307135215.7ba88d83@gandalf.local.home>
On Thu, Mar 07, 2024 at 01:52:15PM -0500, Steven Rostedt wrote:
> On Thu, 7 Mar 2024 16:57:33 +0000
> Mark Rutland <mark.rutland@arm.com> wrote:
>
> > * Use rcu_tasks_trace to synchronize updates?
>
> Yes. I think I wanted both. The above to make sure it covers all cases
> where something could be preempted, and a case for those covered when RCU
> isn't watching (which always has preemption disabled).
>
> My mistake was I thought synchronize_rcu_tasks_rude() did both. But I just
> found out recently that it is not a superset of synchronize_rcu_tasks().
>
> But it really needs it in every location that synchronize_rcu_tasks_rude()
> is called.
Should any RCU Tasks Rude grace-period request also wait for an RCU Tasks
grace period?
I would feel better about proposing this, especially for
call_rcu_tasks_rude(), if RCU Tasks Rude was not supposed to be going
away after all the noinstr tags are in place.
Thanx, Paul
next prev parent reply other threads:[~2024-03-07 18:58 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 15:44 [PATCH] net: raise RCU qs after each threaded NAPI poll Yan Zhai
2024-02-27 16:44 ` Eric Dumazet
2024-02-27 18:32 ` Paul E. McKenney
2024-02-27 21:22 ` Yan Zhai
2024-02-27 22:58 ` Paul E. McKenney
2024-02-28 3:10 ` Jakub Kicinski
2024-02-28 4:42 ` Paul E. McKenney
2024-02-28 14:43 ` Jakub Kicinski
2024-02-28 15:15 ` Paul E. McKenney
2024-02-28 15:35 ` Jakub Kicinski
2024-02-28 15:57 ` Yan Zhai
2024-02-28 11:50 ` Toke Høiland-Jørgensen
2024-02-28 15:10 ` Paul E. McKenney
2024-02-28 15:48 ` Yan Zhai
2024-02-28 17:47 ` Paul E. McKenney
2024-02-28 15:37 ` Joel Fernandes
2024-02-28 16:37 ` Yan Zhai
2024-02-28 17:18 ` Paul E. McKenney
2024-02-28 20:14 ` Joel Fernandes
2024-02-28 21:13 ` Paul E. McKenney
2024-02-28 21:27 ` Joel Fernandes
2024-02-28 21:52 ` Paul E. McKenney
2024-02-28 22:10 ` Joel Fernandes
2024-02-28 22:19 ` Paul E. McKenney
2024-02-28 22:33 ` Steven Rostedt
2024-02-28 22:48 ` Alexei Starovoitov
2024-02-28 22:58 ` Paul E. McKenney
2024-02-29 14:21 ` Joel Fernandes
2024-02-29 16:57 ` Paul E. McKenney
2024-02-29 17:41 ` Joel Fernandes
2024-02-29 18:29 ` Paul E. McKenney
2024-03-02 2:24 ` Joel Fernandes
2024-03-03 0:25 ` Paul E. McKenney
2024-03-03 1:01 ` Joel Fernandes
2024-03-04 9:16 ` Joel Fernandes
2024-03-05 17:53 ` Paul E. McKenney
2024-03-05 19:57 ` Mark Rutland
2024-03-05 21:52 ` Paul E. McKenney
2024-03-06 16:56 ` Steven Rostedt
2024-03-07 16:57 ` Mark Rutland
2024-03-07 18:34 ` Mark Rutland
2024-03-07 18:52 ` Steven Rostedt
2024-03-07 18:58 ` Paul E. McKenney [this message]
2024-03-04 9:16 ` Joel Fernandes
2024-02-28 22:49 ` Paul E. McKenney
2024-02-27 21:17 ` Yan Zhai
2024-02-28 23:53 ` Yan Zhai
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=1165c893-b812-4f88-a1d6-fff85592657e@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=joel@joelfernandes.org \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=rcu@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).