[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170412131325.7c18389d@gandalf.local.home>
Date: Wed, 12 Apr 2017 13:13:25 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: There is a Tasks RCU stall warning
On Wed, 12 Apr 2017 10:07:16 -0700
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:
> > > OK, will optimize it a bit. When are you planning to get this in?
> > >
> >
> > Well, I added the use case for synchronize_rcu_tasks() in my current
> > for-next. I'll have to make sure I get the schedule_idle() in as well
> > as my update to the event benchmark thread as well.
> >
> > I don't think anything will truly break without it yet. But that's
> > assuming there's not another kernel thread somewhere that just spins
> > calling schedule.
> >
> > And this patch will still speed up those that do call
> > synchronize_rcu_tasks(). But that's an optimization and not really a
> > fix.
>
> The upcoming v4.12 merge window, then?
Yep.
-- Steve
Powered by blists - more mailing lists