[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <feb2e1b3-f88e-3022-207f-2862f49a501d@linuxfoundation.org>
Date: Thu, 27 Jun 2019 16:11:51 -0600
From: Shuah Khan <skhan@...uxfoundation.org>
To: paulmck@...ux.ibm.com
Cc: Jiunn Chang <c0d1n61at3@...il.com>,
linux-kernel-mentees@...ts.linuxfoundation.org,
josh@...htriplett.org, rostedt@...dmis.org,
mathieu.desnoyers@...icios.com, jiangshanlai@...il.com,
joel@...lfernandes.org, corbet@....net, rcu@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
"skh >> Shuah Khan" <skhan@...uxfoundation.org>
Subject: Re: [Linux-kernel-mentees][PATCH] doc: RCU callback locks need only
_bh, not necessarily _irq
On 6/27/19 4:10 PM, Paul E. McKenney wrote:
> On Thu, Jun 27, 2019 at 04:01:35PM -0600, Shuah Khan wrote:
>> On 6/27/19 3:01 PM, Jiunn Chang wrote:
>>> The UP.rst file calls for locks acquired within RCU callback functions
>>> to use _irq variants (spin_lock_irqsave() or similar), which does work,
>>> but can be overkill. This commit therefore instead calls for _bh variants
>>> (spin_lock_bh() or similar), while noting that _irq does work.
>>>
>>> Signed-off-by: Paul E. McKenney <paulmck@...ux.ibm.com>
>>
>> Should this by Suggested-by?
>
> I wrote it and Jiunn converted my change to .rst, so I believe that
> this is correct as is.
>
Great.
thanks,
-- Shuah
Powered by blists - more mailing lists