From: Tejun Heo <tj@kernel.org>
To: paulmck@linux.vnet.ibm.com
Cc: lkml <linux-kernel@vger.kernel.org>, mst@redhat.com
Subject: Re: [PATCH RFC] workqueue: remove in_workqueue_context()
Date: Fri, 15 Oct 2010 16:48:44 +0200 [thread overview]
Message-ID: <4CB869CC.7070800@kernel.org> (raw)
In-Reply-To: <20100923171019.GD2406@linux.vnet.ibm.com>
On 09/23/2010 07:10 PM, Paul E. McKenney wrote:
> On Thu, Sep 23, 2010 at 02:35:07PM +0200, Tejun Heo wrote:
>> Commit a25909a4 (lockdep: Add an in_workqueue_context() lockdep-based
>> test function) added in_workqueue_context() but there hasn't been any
>> in-kernel user and the lockdep annotation in workqueue is scheduled to
>> change. Remove the unused function.
>>
>> Signed-off-by: Tejun Heo <tj@kernel.org>
>> Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>> ---
>> Paul, I was looking through lockdep annotations to see how they can be
>> improved and noticed that in_workqueue_context() isn't used by anyone
>> and it seems like there hasn't been any in-kernel user either. Can
>> this be removed or do you expect to use it somewhere?
>
> I added it for the drivers/vhost changes. They were using a
> variant of RCU where executing in workqueue context acted as an RCU
> read-side critical section and where flushing workqueues acted as
> an RCU grace period. The in_workqueue_context() was then passed to
> rcu_dereference_check() to verify correct usage.
>
> But you are right, I don't see it being used any more, though I do still
> see the big block comment documenting this in drivers/vhost/vhost.h.
>
> Michael, what are Tejun and I missing here?
Ping. Shall I go forward with this patch?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-10-15 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 12:35 [PATCH RFC] workqueue: remove in_workqueue_context() Tejun Heo
2010-09-23 17:10 ` Paul E. McKenney
2010-10-15 14:48 ` Tejun Heo [this message]
2010-10-19 9:27 ` Tejun Heo
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=4CB869CC.7070800@kernel.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=paulmck@linux.vnet.ibm.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.