All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Fernandes <joel@joelfernandes.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: rcu@vger.kernel.org, rushikesh.s.kadam@intel.com,
	urezki@gmail.com, neeraj.iitr10@gmail.com, frederic@kernel.org,
	rostedt@goodmis.org
Subject: Re: [PATCH v3 0/5] Implement call_rcu_lazy() and miscellaneous fixes
Date: Fri, 15 Jul 2022 15:40:33 +0000	[thread overview]
Message-ID: <YtGKcScgTh3t4SYS@google.com> (raw)
In-Reply-To: <20220715152937.GA1790663@paulmck-ThinkPad-P17-Gen-1>

On Fri, Jul 15, 2022 at 08:29:37AM -0700, Paul E. McKenney wrote:
> On Fri, Jul 15, 2022 at 03:18:04PM +0000, Joel Fernandes wrote:
> > On Thu, Jul 14, 2022 at 03:21:31PM -0700, Paul E. McKenney wrote:
> > > On Thu, Jul 14, 2022 at 01:51:54PM -0700, Paul E. McKenney wrote:
> > > > On Wed, Jul 13, 2022 at 09:32:32PM +0000, Joel Fernandes (Google) wrote:
> > > > > Hello!
> > > > > 
> > > > > Please find the next improved version of call_rcu_lazy() attached.  The main
> > > > > difference between the previous versions is that:
> > > > > - In v2 rcu_barrier is fixed to not hang (I found this to be due to a missing
> > > > >   GP thread wakeup), now I am limiting this wake up only to rcu_barrier() as
> > > > >   requested by Paul.
> > > > > - Fixed checkpatch and build robot issues.
> > > > > - Some more changes to 'lazy' parameter passing and consolidation of segcblist
> > > > >   functions.
> > > > > - more testing via rcutorture and rcuscale.
> > > > 
> > > > Thank you!  What I am going to do is to pull these into an experimental
> > > > not-for-mainline branch and run the usual set of rcutorture tests.
> > > > I will then take a look at the patches.
> > > 
> > > And there were a few conflicts with the nocb patch series in -rcu.
> > > The allegedly conflict-resolved series is here: joel.2022.07.14a
> > > Please let me know if I messed something up.
> > 
> > Thanks, it looks Ok. There is one robot fix for hexagon's arch where I think
> > TREE_RCU is disabled, could you apply the diff below to patch 1/5 ?
> > 
> > Or, I can also just keep it in my version of 1/5 to go out with the next rev.
> 
> Given that I am not testing on hexagon, I will let you fix this one on
> the next rev.  If someone out there is testing this branch on hexagon,
> they should feel free to apply your patch locally.  ;-)

I am pretty sure this is the feature that was going to make Hexagon widely
adopted, but your call ;-)

thanks,

 - Joel


  reply	other threads:[~2022-07-15 15:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 21:32 [PATCH v3 0/5] Implement call_rcu_lazy() and miscellaneous fixes Joel Fernandes (Google)
2022-07-13 21:32 ` [PATCH 1/5] rcu: Introduce call_rcu_lazy() API implementation Joel Fernandes (Google)
2022-07-13 21:39   ` Joel Fernandes
2022-07-13 21:32 ` [PATCH 2/5] rcu: shrinker for lazy rcu Joel Fernandes (Google)
2022-07-13 21:32 ` [PATCH 3/5] rcuscale: Add laziness and kfree tests Joel Fernandes (Google)
2022-07-13 21:32 ` [PATCH 4/5] fs: Move call_rcu() to call_rcu_lazy() in some paths Joel Fernandes (Google)
2022-07-13 21:32 ` [PATCH 5/5] rcutorture: Add test code for call_rcu_lazy() Joel Fernandes (Google)
2022-07-14 20:51 ` [PATCH v3 0/5] Implement call_rcu_lazy() and miscellaneous fixes Paul E. McKenney
2022-07-14 21:33   ` Joel Fernandes
2022-07-14 22:21   ` Paul E. McKenney
2022-07-15 15:18     ` Joel Fernandes
2022-07-15 15:29       ` Paul E. McKenney
2022-07-15 15:40         ` Joel Fernandes [this message]
2022-07-15 15:50           ` Joel Fernandes
2022-07-15 17:17             ` Paul E. McKenney
2022-08-23 17:19   ` Joel Fernandes

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=YtGKcScgTh3t4SYS@google.com \
    --to=joel@joelfernandes.org \
    --cc=frederic@kernel.org \
    --cc=neeraj.iitr10@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=rushikesh.s.kadam@intel.com \
    --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 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.