Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp5160957ima; Tue, 5 Feb 2019 07:17:47 -0800 (PST) X-Google-Smtp-Source: AHgI3IbXGMxIKckLyhPgZD7QsRMrE/kQJx71NIPTVR07oNXB3mVm8QalICqTBTqLnb3r5hirKCa9 X-Received: by 2002:a62:2e46:: with SMTP id u67mr5410556pfu.3.1549379867797; Tue, 05 Feb 2019 07:17:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549379867; cv=none; d=google.com; s=arc-20160816; b=01m0TGANPtYZfWvIGtYiMNEYhNdnhB1fA6fHQ5TX1VbERyC5CftxSttTRyL3BXa/x/ rsKb348ZqNF4tshyD+cVQvlegBtYc73IdOp4bqrEgbZPW72Z27Wx/V4s/5PCy8tviqtl Lp6/w1e/ITCQh/Q7WY+D0f32z610eXz1oghE45LYEZHis9GoEnYEOBXkiD/OgMvy4MPz y0EHCke5ycmJw0o6oP9Ipio9mZK6rbrIuHSr5++68W6saeAqDjG7bRX3awNtsVxtzfg1 jP7BSTcddSCpO+r1Ul36XQ8JXlExxhZRK6qiGwj6aFLrS25eDS6R/VAjFecgK1HY6ow4 wk/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=usZMdQy9fZoBEygKP4QcCG6hxeOuifXnNAk4nWAFWeQ=; b=wo38sgwwB3TwgMWzz8PrIaX65zOwQ5UvQBkLqe3mmJmKU8NtOimhhfFJfBC17kWMYb ebL9Qd9yFQDr94tFPZj0JuFexLvUlerr30DGXtyRF2fOsaLgLVsKkpiuWu9gli4ej6qg QSppKs2e3lnnzefDWt+vR7EPiLr8YTVyuaz71GQIcqYNdC6fQ6EMy5CxkMwLpS0xZha0 uSPhdf+FFQyc0dghdoGp7iXmcOdNOWBG6zwQ9mTSwkBtmONyPkGeSrQWY4Btb5/s+tmo iLnkZnUNdWaf2u0qQ/G+MrTv18JFyQe8fsjTAimLboj3USiuBg5jNiJ8nJGmYj70Ooox bMGw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i1si3427857pfj.276.2019.02.05.07.17.31; Tue, 05 Feb 2019 07:17:47 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729591AbfBEPRL (ORCPT + 99 others); Tue, 5 Feb 2019 10:17:11 -0500 Received: from mga18.intel.com ([134.134.136.126]:16786 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729174AbfBEPRK (ORCPT ); Tue, 5 Feb 2019 10:17:10 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Feb 2019 07:17:10 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,564,1539673200"; d="scan'208";a="124123918" Received: from unknown (HELO localhost.localdomain) ([10.232.112.69]) by orsmga003.jf.intel.com with ESMTP; 05 Feb 2019 07:17:09 -0800 Date: Tue, 5 Feb 2019 08:16:36 -0700 From: Keith Busch To: Hannes Reinecke Cc: John Garry , Hannes Reinecke , Thomas Gleixner , Christoph Hellwig , Marc Zyngier , "axboe@kernel.dk" , Peter Zijlstra , Michael Ellerman , Linuxarm , "linux-kernel@vger.kernel.org" , "linux-scsi@vger.kernel.org" , "linux-block@vger.kernel.org" Subject: Re: Question on handling managed IRQs when hotplugging CPUs Message-ID: <20190205151632.GA28064@localhost.localdomain> References: <20190129172059.GC17132@localhost.localdomain> <3fe63dab-0791-f476-69c4-9866b70e8520@huawei.com> <86d5028d-44ab-3696-f7fe-828d7655faa9@huawei.com> <745609be-b215-dd2d-c31f-0bd84572f49f@suse.de> <42d149c5-0380-c357-8811-81015159ac04@huawei.com> <20190205145244.GB28023@localhost.localdomain> <0de6dae8-1234-3e3f-d8f3-2d8de47b7f9e@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0de6dae8-1234-3e3f-d8f3-2d8de47b7f9e@suse.com> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 05, 2019 at 04:10:47PM +0100, Hannes Reinecke wrote: > On 2/5/19 3:52 PM, Keith Busch wrote: > > Whichever layer dispatched the IO to a CPU specific context should > > be the one to wait for its completion. That should be blk-mq for most > > block drivers. > > > Indeed. > But we don't provide any mechanisms for that ATM, right? > > Maybe this would be a topic fit for LSF/MM? Right, there's nothing handling this now, and sounds like it'd be a good discussion to bring to the storage track.