Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4902899imu; Tue, 29 Jan 2019 09:22:47 -0800 (PST) X-Google-Smtp-Source: ALg8bN7RXH01+/05LuMoU+jH5ffMvvNwSnEDYhrGOu4g7A3JDz07o3Wh7g9xpQm9SJSI3tF3kumJ X-Received: by 2002:a17:902:1745:: with SMTP id i63mr26223452pli.145.1548782567482; Tue, 29 Jan 2019 09:22:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548782567; cv=none; d=google.com; s=arc-20160816; b=A8SHoIwJFqJKJf20RvWQ/Uz4laVGrSdKpZo8Z8S/reiR4+/GZUN5pGYAT++aknyOwo D6VEISLinOxi42XWevdIxBaOMHU7s2yPED5EKxAoTN+xOICBJMp+iamyvm7XmcrCcVmI GTt2pc3wBXgCqvu/ZVUH52YwHix62kQ8vmOt862SG20DOzAXVMeUpbPyM5KtrhnUQxGO qE5RuCchQTQPDy/zNBWm1S4OmeAIHwpnwZdQw713TdzsOkuy+8zcdefWKPgxzfmIgEE+ rWZ1aGwStb4y6T1iIEbQE9ID0ltgBTm0HnEKNHtqQAttsvqakgrV7uEHjf9B8LorDT5b hwQg== 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=hEmt16ocdo9YE2KOkkGiX6wksydE9PUqwTrhNdbKK7E=; b=ouYkksQ7FYmD5dLpHDA9wxDLkIdu8UoRa3K+UIzyJb3RHbFIYp1q4xNbEYSE/e+o6r pYhHC7lVThq+gw9PHvMCgINB033OwvyWOVkh6bvgZFg4l9K7p9BXTY9+Yx43NXPXTAVv echP4Mikxgw2VW0hr/X3M2CYHWhoXt+cdr07KcsKRAmTywYpnp6jayGMV/i9jyOPO59D cTaGAaiuIM7NvLicZAUJn1Bz7wrNEM1jFQZXn23xg42YMz8cy15Mx8rccW4kUM1znMwO IKLiSw0E9jabb7BwsdJvT2sxnteOfRVH+oFClQFIuTXw14GnmIJxXGTirfWNbJKaOYXV 5/vQ== 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 10si2910999pgl.30.2019.01.29.09.22.23; Tue, 29 Jan 2019 09:22: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 S1729018AbfA2RVs (ORCPT + 99 others); Tue, 29 Jan 2019 12:21:48 -0500 Received: from mga03.intel.com ([134.134.136.65]:19859 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727499AbfA2RVs (ORCPT ); Tue, 29 Jan 2019 12:21:48 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jan 2019 09:21:47 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,537,1539673200"; d="scan'208";a="129872084" Received: from unknown (HELO localhost.localdomain) ([10.232.112.69]) by orsmga002.jf.intel.com with ESMTP; 29 Jan 2019 09:21:47 -0800 Date: Tue, 29 Jan 2019 10:20:59 -0700 From: Keith Busch To: John Garry Cc: "tglx@linutronix.de" , Christoph Hellwig , Marc Zyngier , "axboe@kernel.dk" , Peter Zijlstra , Michael Ellerman , Linuxarm , "linux-kernel@vger.kernel.org" , Hannes Reinecke Subject: Re: Question on handling managed IRQs when hotplugging CPUs Message-ID: <20190129172059.GC17132@localhost.localdomain> References: <20190129154433.GF15302@localhost.localdomain> <757902fc-a9ea-090b-7853-89944a0ce1b5@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <757902fc-a9ea-090b-7853-89944a0ce1b5@huawei.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, Jan 29, 2019 at 05:12:40PM +0000, John Garry wrote: > On 29/01/2019 15:44, Keith Busch wrote: > > > > Hm, we used to freeze the queues with CPUHP_BLK_MQ_PREPARE callback, > > which would reap all outstanding commands before the CPU and IRQ are > > taken offline. That was removed with commit 4b855ad37194f ("blk-mq: > > Create hctx for each present CPU"). It sounds like we should bring > > something like that back, but make more fine grain to the per-cpu context. > > > > Seems reasonable. But we would need it to deal with drivers where they only > expose a single queue to BLK MQ, but use many queues internally. I think > megaraid sas does this, for example. > > I would also be slightly concerned with commands being issued from the > driver unknown to blk mq, like SCSI TMF. I don't think either of those descriptions sound like good candidates for using managed IRQ affinities.