public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Pankaj Raghav <p.raghav@samsung.com>
To: Jens Axboe <axboe@kernel.dk>, <hch@lst.de>
Cc: <gost.dev@samsung.com>, <linux-block@vger.kernel.org>,
	<damien.lemoal@opensource.wdc.com>
Subject: Re: [PATCH v3 2/2] block: use blk_mq_plug() wrapper consistently in the block layer
Date: Thu, 29 Sep 2022 15:41:01 +0200	[thread overview]
Message-ID: <ff8bfd82-d4aa-4263-28c0-9c4788e45da8@samsung.com> (raw)
In-Reply-To: <d9a86bdd-bcba-51e9-16d4-287b333e18ad@kernel.dk>

>> Either of the changes should not have led to a bug in zoned devices:
>>
>> - blk_execute_rq_nowait:
>>   Only passthrough requests can use this function, and plugging can be
>>   performed on those requests in zoned devices. So no issues directly
>>   accessing the plug.
>>
>> - blk_flush_plug in bio_poll:
>>   As we don't plug the requests that require a zone lock in the first
>>   place, flushing should not have any impact. So no issues directly
>>   accessing the plug.
>>
>> This is just a cleanup patch to use this wrapper to get the plug
>> consistently across the block layer.
> 
> While I did suggest to make this consistent and in principle it's
> the right thing to do, it also irks me to add extra checks to paths
> where we know that it's just extra pointless code. Maybe we can
> just comment these two spots? Basically each of the sections above
> could just go into the appropriate file.
> 
The checks should go away, and the plug could be inlined by the compiler if
we don't have CONFIG_BLK_DEV_ZONED. Otherwise, I do agree with you that it
is a pointless check.

I am fine with either, though I prefer what this patch is doing. So if you
feel strongly against calling the blk_mq_plug function, I can turn this
patch into just adding comments as you suggested.

  reply	other threads:[~2022-09-29 13:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220929074747eucas1p1821a5b79ad24cb559b7b6ec324239e9e@eucas1p1.samsung.com>
2022-09-29  7:47 ` [PATCH v3 0/2] plugging cleanup v3 Pankaj Raghav
2022-09-29  7:47   ` [PATCH v3 1/2] block: adapt blk_mq_plug() to not plug for writes that require a zone lock Pankaj Raghav
2022-09-29  8:14     ` Damien Le Moal
2022-09-29  8:34     ` Johannes Thumshirn
2022-09-29  7:47   ` [PATCH v3 2/2] block: use blk_mq_plug() wrapper consistently in the block layer Pankaj Raghav
2022-09-29  8:15     ` Damien Le Moal
2022-09-29  8:35     ` Johannes Thumshirn
2022-09-29 13:24     ` Jens Axboe
2022-09-29 13:41       ` Pankaj Raghav [this message]
2022-09-29 13:45         ` Jens Axboe
2022-09-29 13:48           ` Pankaj Raghav
2022-09-29 13:46   ` (subset) [PATCH v3 0/2] plugging cleanup v3 Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ff8bfd82-d4aa-4263-28c0-9c4788e45da8@samsung.com \
    --to=p.raghav@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=gost.dev@samsung.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox