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 X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,UNPARSEABLE_RELAY,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 49ED6C433ED for ; Thu, 15 Apr 2021 01:34:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2717461158 for ; Thu, 15 Apr 2021 01:34:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229450AbhDOBfB (ORCPT ); Wed, 14 Apr 2021 21:35:01 -0400 Received: from out30-57.freemail.mail.aliyun.com ([115.124.30.57]:53117 "EHLO out30-57.freemail.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229449AbhDOBfB (ORCPT ); Wed, 14 Apr 2021 21:35:01 -0400 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R151e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e04420;MF=jefflexu@linux.alibaba.com;NM=1;PH=DS;RN=7;SR=0;TI=SMTPD_---0UVaqHuM_1618450476; Received: from admindeMacBook-Pro-2.local(mailfrom:jefflexu@linux.alibaba.com fp:SMTPD_---0UVaqHuM_1618450476) by smtp.aliyun-inc.com(127.0.0.1); Thu, 15 Apr 2021 09:34:37 +0800 Subject: Re: [PATCH V5 11/12] block: add poll_capable method to support bio-based IO polling To: Ming Lei Cc: Christoph Hellwig , Jens Axboe , linux-block@vger.kernel.org, Mike Snitzer , dm-devel@redhat.com, Hannes Reinecke References: <20210401021927.343727-1-ming.lei@redhat.com> <20210401021927.343727-12-ming.lei@redhat.com> <20210412093856.GA978201@infradead.org> From: JeffleXu Message-ID: <5f30059d-6650-8268-b681-d8567ac1c509@linux.alibaba.com> Date: Thu, 15 Apr 2021 09:34:36 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On 4/14/21 7:24 PM, Ming Lei wrote: > On Wed, Apr 14, 2021 at 04:38:25PM +0800, JeffleXu wrote: >> >> >> On 4/12/21 5:38 PM, Christoph Hellwig wrote: >>> On Thu, Apr 01, 2021 at 10:19:26AM +0800, Ming Lei wrote: >>>> From: Jeffle Xu >>>> >>>> This method can be used to check if bio-based device supports IO polling >>>> or not. For mq devices, checking for hw queue in polling mode is >>>> adequate, while the sanity check shall be implementation specific for >>>> bio-based devices. For example, dm device needs to check if all >>>> underlying devices are capable of IO polling. >>>> >>>> Though bio-based device may have done the sanity check during the >>>> device initialization phase, cacheing the result of this sanity check >>>> (such as by cacheing in the queue_flags) may not work. Because for dm >>>> devices, users could change the state of the underlying devices through >>>> '/sys/block//io_poll', bypassing the dm device above. In this case, >>>> the cached result of the very beginning sanity check could be >>>> out-of-date. Thus the sanity check needs to be done every time 'io_poll' >>>> is to be modified. >>> >>> I really don't think thi should be a method, and I really do dislike >>> how we have all this "if (is_mq)" junk. Why can't we have a flag on >>> the gendisk that signals if the device can support polling that >>> is autoamtically set for blk-mq and as-needed by bio based drivers? >> >> That would consume one more bit of queue->queue_flags. >> >> Besides, DM/MD is somehow special here that when one of the underlying >> devices is disabled polling through '/sys/block//io_poll', >> currently there's no mechanism notifying the above MD/DM to clear the >> previously set queue_flags. Thus the outdated queue_flags still >> indicates this DM/MD is capable of polling, while in fact one of the >> underlying device has been disabled for polling. > > Right, just like there isn't queue limit progagation. > > Another blocker could be that bio based queue doesn't support queue > freezing. Do you mean the queue freezing is called in the following code snippet? ``` static ssize_t queue_poll_store(struct request_queue *q, const char *page, size_t count) { ... if (poll_on) { blk_queue_flag_set(QUEUE_FLAG_POLL, q); } else { blk_mq_freeze_queue(q); blk_queue_flag_clear(QUEUE_FLAG_POLL, q); blk_mq_unfreeze_queue(q); } ``` And I can't understand how bio-based queue doesn't support queue freezing. ``` submit_bio_noacct __submit_bio_noacct bio_queue_enter ``` Every time submitting a bio, bio_queue_enter() will be called, and once the queue has been frozen, bio_queue_enter() will wait there until the queue is unfrozen. > >> >> Mike had ever suggested that we can trust the queue_flag, and clear the >> outdated queue_flags when later the IO submission or polling routine >> finally finds that the device is not capable of polling. Currently >> submit_bio_checks() will silently clear the REQ_HIPRI flag and still >> submit the bio when the device is actually not capable of polling. To >> fix the issue, could we break the submission and return an error code in >> submit_bio_checks() if the device is not capable of polling when >> submitting HIPRI bio? > > I think we may just leave it alone, if underlying queue becomes not pollable, > the bio still can be submitted & completed via IRQ, just not efficient enough. Yes it still works. I agree if there's no better solution... And what about the issue Christoph originally concerned? Do we use one more flag bit indicating if the queue capable of polling, or the poll_capable() method way? -- Thanks, Jeffle 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 X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,UNPARSEABLE_RELAY,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 54D4EC433B4 for ; Fri, 16 Apr 2021 08:21:30 +0000 (UTC) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 9960361184 for ; Fri, 16 Apr 2021 08:21:29 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9960361184 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.alibaba.com Authentication-Results: mail.kernel.org; spf=tempfail smtp.mailfrom=dm-devel-bounces@redhat.com Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-546-1d9a7bsZNGi3sfwWJ5pIKw-1; Fri, 16 Apr 2021 04:21:26 -0400 X-MC-Unique: 1d9a7bsZNGi3sfwWJ5pIKw-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 60A6D83DD20; Fri, 16 Apr 2021 08:21:22 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A003910074E1; Fri, 16 Apr 2021 08:21:21 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id 15C861806D0F; Fri, 16 Apr 2021 08:21:20 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 13F1YnKs015270 for ; Wed, 14 Apr 2021 21:34:49 -0400 Received: by smtp.corp.redhat.com (Postfix) id 16D35F6433; Thu, 15 Apr 2021 01:34:49 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast06.extmail.prod.ext.rdu2.redhat.com [10.11.55.22]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 10CA29D7C for ; Thu, 15 Apr 2021 01:34:45 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [207.211.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id C1CB2185A7A7 for ; Thu, 15 Apr 2021 01:34:45 +0000 (UTC) Received: from out30-54.freemail.mail.aliyun.com (out30-54.freemail.mail.aliyun.com [115.124.30.54]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-1-znM_rbtZPTOBXD1XzJ79iA-1; Wed, 14 Apr 2021 21:34:41 -0400 X-MC-Unique: znM_rbtZPTOBXD1XzJ79iA-1 X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R151e4; CH=green; DM=||false|; DS=||; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e01e04420; MF=jefflexu@linux.alibaba.com; NM=1; PH=DS; RN=7; SR=0; TI=SMTPD_---0UVaqHuM_1618450476 Received: from admindeMacBook-Pro-2.local(mailfrom:jefflexu@linux.alibaba.com fp:SMTPD_---0UVaqHuM_1618450476) by smtp.aliyun-inc.com(127.0.0.1); Thu, 15 Apr 2021 09:34:37 +0800 To: Ming Lei References: <20210401021927.343727-1-ming.lei@redhat.com> <20210401021927.343727-12-ming.lei@redhat.com> <20210412093856.GA978201@infradead.org> From: JeffleXu Message-ID: <5f30059d-6650-8268-b681-d8567ac1c509@linux.alibaba.com> Date: Thu, 15 Apr 2021 09:34:36 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: X-Mimecast-Impersonation-Protect: Policy=CLT - Impersonation Protection Definition; Similar Internal Domain=false; Similar Monitored External Domain=false; Custom External Domain=false; Mimecast External Domain=false; Newly Observed Domain=false; Internal User Name=false; Custom Display Name List=false; Reply-to Address Mismatch=false; Targeted Threat Dictionary=false; Mimecast Threat Dictionary=false; Custom Threat Dictionary=false X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-loop: dm-devel@redhat.com X-Mailman-Approved-At: Fri, 16 Apr 2021 04:21:18 -0400 Cc: Jens Axboe , linux-block@vger.kernel.org, Mike Snitzer , Christoph Hellwig , dm-devel@redhat.com Subject: Re: [dm-devel] [PATCH V5 11/12] block: add poll_capable method to support bio-based IO polling X-BeenThere: dm-devel@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: device-mapper development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dm-devel-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On 4/14/21 7:24 PM, Ming Lei wrote: > On Wed, Apr 14, 2021 at 04:38:25PM +0800, JeffleXu wrote: >> >> >> On 4/12/21 5:38 PM, Christoph Hellwig wrote: >>> On Thu, Apr 01, 2021 at 10:19:26AM +0800, Ming Lei wrote: >>>> From: Jeffle Xu >>>> >>>> This method can be used to check if bio-based device supports IO polling >>>> or not. For mq devices, checking for hw queue in polling mode is >>>> adequate, while the sanity check shall be implementation specific for >>>> bio-based devices. For example, dm device needs to check if all >>>> underlying devices are capable of IO polling. >>>> >>>> Though bio-based device may have done the sanity check during the >>>> device initialization phase, cacheing the result of this sanity check >>>> (such as by cacheing in the queue_flags) may not work. Because for dm >>>> devices, users could change the state of the underlying devices through >>>> '/sys/block//io_poll', bypassing the dm device above. In this case, >>>> the cached result of the very beginning sanity check could be >>>> out-of-date. Thus the sanity check needs to be done every time 'io_poll' >>>> is to be modified. >>> >>> I really don't think thi should be a method, and I really do dislike >>> how we have all this "if (is_mq)" junk. Why can't we have a flag on >>> the gendisk that signals if the device can support polling that >>> is autoamtically set for blk-mq and as-needed by bio based drivers? >> >> That would consume one more bit of queue->queue_flags. >> >> Besides, DM/MD is somehow special here that when one of the underlying >> devices is disabled polling through '/sys/block//io_poll', >> currently there's no mechanism notifying the above MD/DM to clear the >> previously set queue_flags. Thus the outdated queue_flags still >> indicates this DM/MD is capable of polling, while in fact one of the >> underlying device has been disabled for polling. > > Right, just like there isn't queue limit progagation. > > Another blocker could be that bio based queue doesn't support queue > freezing. Do you mean the queue freezing is called in the following code snippet? ``` static ssize_t queue_poll_store(struct request_queue *q, const char *page, size_t count) { ... if (poll_on) { blk_queue_flag_set(QUEUE_FLAG_POLL, q); } else { blk_mq_freeze_queue(q); blk_queue_flag_clear(QUEUE_FLAG_POLL, q); blk_mq_unfreeze_queue(q); } ``` And I can't understand how bio-based queue doesn't support queue freezing. ``` submit_bio_noacct __submit_bio_noacct bio_queue_enter ``` Every time submitting a bio, bio_queue_enter() will be called, and once the queue has been frozen, bio_queue_enter() will wait there until the queue is unfrozen. > >> >> Mike had ever suggested that we can trust the queue_flag, and clear the >> outdated queue_flags when later the IO submission or polling routine >> finally finds that the device is not capable of polling. Currently >> submit_bio_checks() will silently clear the REQ_HIPRI flag and still >> submit the bio when the device is actually not capable of polling. To >> fix the issue, could we break the submission and return an error code in >> submit_bio_checks() if the device is not capable of polling when >> submitting HIPRI bio? > > I think we may just leave it alone, if underlying queue becomes not pollable, > the bio still can be submitted & completed via IRQ, just not efficient enough. Yes it still works. I agree if there's no better solution... And what about the issue Christoph originally concerned? Do we use one more flag bit indicating if the queue capable of polling, or the poll_capable() method way? -- Thanks, Jeffle -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel