public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH] null_blk: allow REQ_OP_ZONE_RESET_ALL to configure
Date: Wed, 19 Oct 2022 06:17:31 +0000	[thread overview]
Message-ID: <03102f4c-fcfe-ec47-0878-bc25c8a1a5bb@nvidia.com> (raw)
In-Reply-To: <a54a9c84-0dd6-4af6-6c6e-d67d9e5a8695@opensource.wdc.com>

Damien,

  MODULE_PARM_DESC(zone_max_active, "Maximum number of active zones when 
block device is zoned. Default: 0 (no limit)");
>>>>    
>>>> +static bool g_zone_reset_all = true;
>>>> +module_param_named(zone_reset_all, g_zone_reset_all, bool, 0444);
>>>
>>> Nit: Why read-only ? You can make it writable without any issue, no ?
>>>
>>
>> Sorry I didn't understand this comment. In case this comment is about
>> new zone_reset_all modpram being readonly and not allowed to set via
>> command line? The test log shows I was able to set it to 0 and trigger
>> call to blkdev_zone_reset_all_emulated() and default behavior ends up
>> calling blkdev_zone_reset_all().
>>
>> -ck
>>
> 
> If you change the param mode to 644, one can do:
> 
> echo 0 >/sys/module/null_blk/parameters/zone_reset_all
> or
> echo 1 >/sys/module/null_blk/parameters/zone_reset_all
> 
> But given that all null_blk parameters are read-only, not a big deal.
> 

if you are okay with this can I get your reviewed-by ?

-ck


  reply	other threads:[~2022-10-19  6:17 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 [this message]
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
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=03102f4c-fcfe-ec47-0878-bc25c8a1a5bb@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=damien.lemoal@opensource.wdc.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