From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E9149EB64D9 for ; Wed, 12 Jul 2023 13:19:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232146AbjGLNTb (ORCPT ); Wed, 12 Jul 2023 09:19:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47620 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229596AbjGLNTa (ORCPT ); Wed, 12 Jul 2023 09:19:30 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3D4D5E65; Wed, 12 Jul 2023 06:19:29 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 67AE967373; Wed, 12 Jul 2023 15:19:25 +0200 (CEST) Date: Wed, 12 Jul 2023 15:19:25 +0200 From: Christoph Hellwig To: Ming Lei Cc: Christoph Hellwig , Jens Axboe , linux-nvme@lists.infradead.org, "Martin K . Petersen" , linux-scsi@vger.kernel.org, linux-block@vger.kernel.org, Wen Xiong , Keith Busch , Thomas Gleixner , linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/8] blk-mq: add blk_mq_max_nr_hw_queues() Message-ID: <20230712131925.GA14596@lst.de> References: <20230712125455.1986455-1-ming.lei@redhat.com> <20230712125455.1986455-2-ming.lei@redhat.com> <20230712130017.GA12417@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-scsi@vger.kernel.org On Wed, Jul 12, 2023 at 09:16:11PM +0800, Ming Lei wrote: > The problem is that blk_mq_alloc_tag_set() forces to set nr_hw_queues > as 1 for kdump kernel, that is why blk_mq_max_nr_hw_queues() has to > return 1 for kdump kernel. Well, let's fix that first and work from there. Same argument against that deep magic applies there as well. > Thomas, can we disable managed irq for kdump kernel and switch to > non-managed irq? Then we can avoid driver's change. I'd suggest > this way if it is possible. Why the heck would we?