Received: by 2002:a05:6358:a55:b0:ec:fcf4:3ecf with SMTP id 21csp331360rwb; Wed, 18 Jan 2023 18:32:47 -0800 (PST) X-Google-Smtp-Source: AMrXdXuHWtyLuXuxx/nvApLXkFI/Wv41m9J6Lyie9YGNJV5wkq7wXQzl4ijkrjZLWMzoC6je5rFc X-Received: by 2002:a17:902:b095:b0:192:bdf8:1a5c with SMTP id p21-20020a170902b09500b00192bdf81a5cmr9706824plr.33.1674095567440; Wed, 18 Jan 2023 18:32:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1674095567; cv=none; d=google.com; s=arc-20160816; b=C4cetU5yU64HXcopsYyk2fXX7W1+xsiH0n+ZKaX4j4SnaxYuJVL8iojMlWz7zypBqx KdsfNpFsMe1SNUU6ceyxQ4UBHhwt9bDeGAFYzVsZTuEbo0syPflNdmYZywz+OJiV+0hj 7z6bsNrOY5EGLxCZx1Ogyt3XiuAuyK8aqGoY2SD/RsgwnD4usIE5ZBmJrY/m09HkIXZl YKHT1DklDMMqSNWoOs5GPYhoQ2I5IqdetGwXz9/Z4xqqWqTdAlk58iyFBvtF66yHxR+z NlL86fxqYZDWVyY8Ay03sua3w0UizzL5/vExH2EYSuom4JHTjyshkJV3jjOE+2nC++oD uLyg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=Ux/ppRsSEVsjt/Jmk3872uyi+oFHtH4Cuq+HJnev+I4=; b=vnTXK95OoW4soCuqKhnh3pzZg28Q0TcOJd/B+e6mPHu68N/79k5Mc0NjbbRBpfgICD S+BKD0RPYsKedNNEVjm6Xr6rLY4wD5iJoUjz2Xc5FhfMO2Ji/p7LD+0PBknL11zVqzoH KvSzCUylfAAn00AV/qPebjVSTNOi+B+EDlU9Ee+scBoIMUT2+QgQSKeTqAGUFWU5b8zr RU+IjyCC1DUVi/UUjq4Va8W/DoZ6a6H8ibkZxoQCikhCGZUgdpfej7yWeywTEIoxw8Wm YlBARyliOKAYt4Qi7AvwR5kA+1rAlx6SBzKCcyop+99LUkO753zeja6ekiQwH1eHk3l3 IvIQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u18-20020a170902e81200b0017e8aa47020si1786606plg.472.2023.01.18.18.32.32; Wed, 18 Jan 2023 18:32:47 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229843AbjASBsY (ORCPT + 44 others); Wed, 18 Jan 2023 20:48:24 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50766 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229832AbjASBpm (ORCPT ); Wed, 18 Jan 2023 20:45:42 -0500 Received: from dggsgout12.his.huawei.com (unknown [45.249.212.56]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 31BE96CCD1; Wed, 18 Jan 2023 17:40:34 -0800 (PST) Received: from mail02.huawei.com (unknown [172.30.67.169]) by dggsgout12.his.huawei.com (SkyGuard) with ESMTP id 4Ny5166LGDz4f3v6d; Thu, 19 Jan 2023 09:40:26 +0800 (CST) Received: from [10.174.178.129] (unknown [10.174.178.129]) by APP1 (Coremail) with SMTP id cCh0CgCXAy6Ln8hj1mNwBw--.27187S2; Thu, 19 Jan 2023 09:40:29 +0800 (CST) Subject: Re: [PATCH v4 07/14] blk-mq: make blk_mq_commit_rqs a general function for all commits To: Christoph Hellwig Cc: axboe@kernel.dk, dwagner@suse.de, hare@suse.de, ming.lei@redhat.com, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, john.garry@huawei.com, jack@suse.cz References: <20230118093726.3939160-1-shikemeng@huaweicloud.com> <20230118093726.3939160-7-shikemeng@huaweicloud.com> <20230118173745.GC12399@lst.de> From: Kemeng Shi Message-ID: Date: Thu, 19 Jan 2023 09:40:27 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 In-Reply-To: <20230118173745.GC12399@lst.de> Content-Type: text/plain; charset=gbk Content-Transfer-Encoding: 7bit X-CM-TRANSID: cCh0CgCXAy6Ln8hj1mNwBw--.27187S2 X-Coremail-Antispam: 1UD129KBjvdXoW7GFyDCr1xXr45JF1DJryxZrb_yoWkXFgE9F yakrykWw4DWws2kws2kF43XFW8Ka4kXF98tF4DtFyrGrykJrZ5GFyDXFn8Zay7Gw42yF1f AF9xZ3WUCrnFgjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUbzAYFVCjjxCrM7AC8VAFwI0_Gr0_Xr1l1xkIjI8I6I8E6xAIw20E Y4v20xvaj40_Wr0E3s1l1IIY67AEw4v_Jr0_Jr4l8cAvFVAK0II2c7xJM28CjxkF64kEwV A0rcxSw2x7M28EF7xvwVC0I7IYx2IY67AKxVWDJVCq3wA2z4x0Y4vE2Ix0cI8IcVCY1x02 67AKxVW8Jr0_Cr1UM28EF7xvwVC2z280aVAFwI0_GcCE3s1l84ACjcxK6I8E87Iv6xkF7I 0E14v26rxl6s0DM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVACY4xI64kE6c02F40E x7xfMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8JwAm72CE4IkC6x 0Yz7v_Jr0_Gr1lF7xvr2IY64vIr41lc7I2V7IY0VAS07AlzVAYIcxG8wCF04k20xvY0x0E wIxGrwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c02F40E14v26r1j6r18MI8I3I0E74 80Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jw0_GFylIxkGc2Ij64vIr41lIxAIcVC0 I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr1lIxAIcVCF04 k26cxKx2IYs7xG6rW3Jr0E3s1lIxAIcVC2z280aVAFwI0_Jr0_Gr1lIxAIcVC2z280aVCY 1x0267AKxVWUJVW8JbIYCTnIWIevJa73UjIFyTuYvjxUrR6zUUUUU X-CM-SenderInfo: 5vklyvpphqwq5kxd4v5lfo033gof0z/ X-CFilter-Loop: Reflected X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,KHOP_HELO_FCRDNS, NICE_REPLY_A,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org on 1/19/2023 1:37 AM, Christoph Hellwig wrote: > On Wed, Jan 18, 2023 at 05:37:19PM +0800, Kemeng Shi wrote: >> +/* >> + * blk_mq_commit_rqs will notify driver using bd->last that there is no >> + * more requests. (See comment in struct blk_mq_ops for commit_rqs for >> + * details) >> + * Attention, we should explicitly call this in unusual cases: >> + * 1) did not queue everything initially scheduled to queue >> + * 2) the last attempt to queue a request failed >> + */ >> +static void blk_mq_commit_rqs(struct blk_mq_hw_ctx *hctx, int queued, >> + bool from_schedule) > > Isn't from_schedule always false here as well now? Hi Christoph , Yes, it's always false now. As blk_mq_commit_rqs is a general function for all commits now, I keep the from_schedule for commits where from_schedule maybe true in future. We can remove from_schedule now and add it back when from_schedule is indeed needed. Both way is acceptable for me. Please let me know which way do you prefer and I will send a new version if needed. Thanks. > Otherwise looks good: > > Reviewed-by: Christoph Hellwig > -- Best wishes Kemeng Shi