Re: [PATCH] NVMe: do not touch sq door bell if nvmeq has been suspended

From	Keith Busch <keith.busch@intel.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH] NVMe: do not touch sq door bell if nvmeq has been suspended
Date	2016-02-10 00:00 +0100
Message-ID	<r0pqi-251-25@gated-at.bofh.it> (permalink)
References	(4 earlier) <qY8Df-4ol-3@gated-at.bofh.it> <qY8Df-4ol-1@gated-at.bofh.it> <qZxSW-6QG-7@gated-at.bofh.it> <qZVBT-70K-1@gated-at.bofh.it> <r0pqi-251-27@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Tue, Feb 09, 2016 at 11:22:04AM +0000, Wenbo Wang wrote:
> In most cases, rcu read lock is just a preempt_disable, which is what get_cpu does. I don't see any risk.

Yes, many rcu_read_lock cases expand similarly to get_cpu. What about
the other cases?

FWIW, I don't think we'll hit the problem with the proposed rcu sync.
Heck, we don't even have a synchronize today and we don't hit the
theoretical problem.

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: [PATCH] NVMe: do not touch sq door bell if nvmeq has been  suspended Keith Busch <keith.busch@intel.com> - 2016-02-10 00:00 +0100

csiph-web