Received: by 10.223.176.46 with SMTP id f43csp460869wra; Fri, 26 Jan 2018 01:33:14 -0800 (PST) X-Google-Smtp-Source: AH8x226fQAZOsbojL2hWxq+cxV6XrIycQjT+zVAB/vAPJaHja//sdm01+HS3tKNjC69dOjGJIXyS X-Received: by 10.99.50.66 with SMTP id y63mr14975094pgy.157.1516959194708; Fri, 26 Jan 2018 01:33:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516959194; cv=none; d=google.com; s=arc-20160816; b=kCsCGtyu+gwNBRp2OsF3Y8S8+OTG46y3zyvS7rp7wOOakyjQSsqj2lN7z1dBAretVb EgguNW/rukquJtdILqpGF3DK5H2EEaCIeu/y7xzWpd2mje2AijeZCXVn/puri9FOdrch TWGF7SWQZp2TJv2WmDWgQZRoidbrUzoa5j3XPf4US8dVcwEVZxcPIi1/u2ZJW0veVjDT IzIPQxmyYbrYS3hpj4cKp7BNTJFeZq95aLUWUvsCLlRPm/J28WZ+I3K9ZQD0Et2KEBcO 5eZxPMFBliR+2RLLHbbjrdxLBLMbDnDpjh54yOIkY8s8Ct/ClGuwFTTsTNv7DW2BuxaA U5Ig== 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:arc-authentication-results; bh=FtsjmWiC+Xb8TTZmSlDyKU5jAaBVVw09OJYA1ZiN4lM=; b=l/W8wRdfjhMuKpyO7UpUVvqToVTa+i6L66sX1Yolh4opz4GRisWtUIh4S3pxkMIr/i lwEtrUc5ONOq43KBui/HhYdrON8xk+68D+v39OITDO2ZhxIOW58+Mnlq1h8uPne76aAu TqNl3630vtZqmoMPwnuwkjesca7OT/O0eJtmQkQh1OEejMiDpGaQ5uTNfwlD5TQ5LFR/ KwConz3kGIQMOysiJdkMgoeOvmXKm9Mr3p8fCADitqyjxhCGKPSWmxbKQHsbv/emIPJj TMcB0qJy/vaM50KhstqJL/VgMPk6Zn4674tlzl3FOQN7p0Fi65B0AXoTWKEAywGGd6ca HQlA== 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t5-v6si3439635plo.662.2018.01.26.01.32.59; Fri, 26 Jan 2018 01:33:14 -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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752828AbeAZJcB (ORCPT + 99 others); Fri, 26 Jan 2018 04:32:01 -0500 Received: from mx1.redhat.com ([209.132.183.28]:56096 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752511AbeAZJb7 (ORCPT ); Fri, 26 Jan 2018 04:31:59 -0500 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id DEEC6C04C3BD; Fri, 26 Jan 2018 09:31:58 +0000 (UTC) Received: from ming.t460p (ovpn-12-128.pek2.redhat.com [10.72.12.128]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 49F055D720; Fri, 26 Jan 2018 09:31:42 +0000 (UTC) Date: Fri, 26 Jan 2018 17:31:38 +0800 From: Ming Lei To: "jianchao.wang" Cc: Keith Busch , Sagi Grimberg , Christoph Hellwig , Jens Axboe , Stefan Haberland , linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, James Smart , linux-block@vger.kernel.org, Christian Borntraeger , Thomas Gleixner , Christoph Hellwig Subject: Re: [PATCH 2/2] blk-mq: simplify queue mapping & schedule with each possisble CPU Message-ID: <20180126093129.GA10926@ming.t460p> References: <20180116121010.GA26429@ming.t460p> <7c24e321-2d3b-cdec-699a-f58c34300aa9@oracle.com> <20180116153248.GA3018@ming.t460p> <7f5bad86-febc-06fc-67c0-393777d172e4@oracle.com> <20180117035159.GA9487@ming.t460p> <8c8efce8-ea02-0a9e-8369-44c885f4731d@oracle.com> <20180117062251.GC9487@ming.t460p> <977e9c62-c7f2-d1df-7d6b-5903f3b21cb6@oracle.com> <20180117095744.GF9487@ming.t460p> <53da00dc-3d46-dcdb-2be4-277f79a9888b@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53da00dc-3d46-dcdb-2be4-277f79a9888b@oracle.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Fri, 26 Jan 2018 09:31:59 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jianchao, On Fri, Jan 19, 2018 at 11:05:35AM +0800, jianchao.wang wrote: > Hi ming > > Sorry for delayed report this. > > On 01/17/2018 05:57 PM, Ming Lei wrote: > > 2) hctx->next_cpu can become offline from online before __blk_mq_run_hw_queue > > is run, there isn't warning, but once the IO is submitted to hardware, > > after it is completed, how does the HBA/hw queue notify CPU since CPUs > > assigned to this hw queue(irq vector) are offline? blk-mq's timeout > > handler may cover that, but looks too tricky. > > In theory, the irq affinity will be migrated to other cpu. This is done by Yes, but the other CPU should belong to this irq's affinity, and if all CPUs in the irq's affinity is DEAD, this irq vector will be shutdown, and if there is in-flight IO or will be, then the completion for this IOs won't be delivered to CPUs. And now seems we depend on queue's timeout handler to handle them. > fixup_irqs() in the context of stop_machine. > However, in my test, I found this log: > > [ 267.161043] do_IRQ: 7.33 No irq handler for vector > > The 33 is the vector used by nvme cq. > The irq seems to be missed and sometimes IO hang occurred. As I mentioned above, it shouldn't be strange to see in CPU offline/online stress test. -- Ming