From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756739AbbEUTec (ORCPT ); Thu, 21 May 2015 15:34:32 -0400 Received: from mga14.intel.com ([192.55.52.115]:37476 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756675AbbEUTeW (ORCPT ); Thu, 21 May 2015 15:34:22 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,471,1427785200"; d="scan'208";a="713847256" Date: Thu, 21 May 2015 19:34:20 +0000 (UTC) From: Keith Busch X-X-Sender: vmware@localhost.lm.intel.com To: Parav Pandit cc: linux-nvme@lists.infradead.org, willy@linux.intel.com, axboe@kernel.dk, linux-kernel@vger.kernel.org Subject: Re: [PATCH] NVMe: Avoid interrupt disable during queue init. In-Reply-To: <1432253553-17045-1-git-send-email-parav.pandit@avagotech.com> Message-ID: References: <1432253553-17045-1-git-send-email-parav.pandit@avagotech.com> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 21 May 2015, Parav Pandit wrote: > Avoid diabling interrupt and holding q_lock for the queue > which is just getting initialized. > > With this change, online_queues is also incremented without > lock during queue setup stage. > if Power management nvme_suspend() kicks in during queue setup time, > per nvmeq based q_lock spinlock cannot protect device wide > online_queues variable anyway. The q_lock is held to protect polling from reading inconsistent data.