public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Fu <vincent.fu@samsung.com>
To: "kch@nvidia.com" <kch@nvidia.com>,
	Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Vincent Fu <vincent.fu@samsung.com>
Subject: Re: [PATCH] null_blk: allow REQ_OP_ZONE_RESET_ALL to configure
Date: Fri, 4 Nov 2022 18:52:07 +0000	[thread overview]
Message-ID: <20221104185124.181754-1-vincent.fu@samsung.com> (raw)
In-Reply-To: <6270de4e-9f4a-fcfc-c4f1-d0ede32352bb@nvidia.com>

On Wed, Nov 02, 2022 at 12:52:06AM +0000, Chaitanya Kulkarni wrote:
>On 10/27/22 13:07, Vincent Fu wrote:
>> On Wed, Oct 05, 2022 at 10:05:13PM -0700, Chaitanya Kulkarni wrote:
>>> For a Zoned Block Device zone reset all is emulated if underlaying
>>> device doesn't support REQ_OP_ZONE_RESET_ALL operation. In null_blk
>>> Zoned mode there is no way to test zone reset all emulation present in
>>> the block layer since we enable it by default :-
>>>
>>> blkdev_zone_mgmt()
>>> blkdev_zone_reset_all_emulation() <---
>>> blkdev_zone_reset_all()
>>>
>>> Add a module parameter zone_reset_all to enable or disable
>>> REQ_OP_ZONE_RESET_ALL, enable it by default to retain the existing
>>> behaviour.
>>>
>>> Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com>
>>
>> For the sake of completeness would it be reasonable to also provide a
>> means to set this option via configfs?
>>
>> Vincent
>
>I deliberately avoided that as I don't see any need for it as of now.
>but if it is a hard requirement I Can certainly send V2 with configfs
>param.
>
>-ck

I think the default should be to have features available as both module
options and via configfs unless there are good reasons to make an
exception.

https://lore.kernel.org/linux-block/f0dadb60-c02d-d569-3004-81eafeebb95f@kernel.dk/
https://lore.kernel.org/linux-block/ca206223-112f-2d60-34a3-bb7e6295de7a@kernel.dk/

Vincent

  reply	other threads:[~2022-11-04 18:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221027200756uscas1p206196106ee2224a7653f1f2bc7ba31e9@uscas1p2.samsung.com>
2022-10-06  5:05 ` [PATCH] null_blk: allow REQ_OP_ZONE_RESET_ALL to configure Chaitanya Kulkarni
2022-10-06  5:15   ` Damien Le Moal
2022-10-07  5:38     ` Chaitanya Kulkarni
2022-10-07  6:08       ` Damien Le Moal
2022-10-19  6:17         ` Chaitanya Kulkarni
2022-10-19  6:44   ` Damien Le Moal
2022-10-27 20:07   ` Vincent Fu
2022-11-02  0:52     ` Chaitanya Kulkarni
2022-11-04 18:52       ` Vincent Fu [this message]
2022-11-05 15:24         ` Jens Axboe
2022-11-05 16:35           ` Chaitanya Kulkarni

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=20221104185124.181754-1-vincent.fu@samsung.com \
    --to=vincent.fu@samsung.com \
    --cc=chaitanyak@nvidia.com \
    --cc=kch@nvidia.com \
    --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