From: Nilay Shroff <nilay@linux.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
kbusch@kernel.org, hare@suse.de, sagi@grimberg.me,
jmeneghi@redhat.com, axboe@kernel.dk, martin.petersen@oracle.com,
gjoyce@ibm.com
Subject: Re: [RFC PATCHv2 2/3] nvme: introduce multipath_head_always module param
Date: Tue, 29 Apr 2025 11:56:05 +0530 [thread overview]
Message-ID: <9a4245ed-bd5d-4a42-b8ef-3d4e557c69c8@linux.ibm.com> (raw)
In-Reply-To: <20250425144540.GB12179@lst.de>
On 4/25/25 8:15 PM, Christoph Hellwig wrote:
> On Fri, Apr 25, 2025 at 04:03:09PM +0530, Nilay Shroff wrote:
>> +static int multipath_param_set(const char *val, const struct kernel_param *kp)
>> +{
>> + int ret;
>> +
>> + ret = param_set_bool(val, kp);
>> + if (ret)
>> + return ret;
>> +
>> + if (multipath_head_always && !*(bool *)kp->arg) {
>> + pr_err("Can't disable multipath when multipath_head_always is configured.\n");
>> + *(bool *)kp->arg = true;
>
> This reads much nicer if you add a local bool * variable and avoid
> all the casting, i.e.
>
> bool *arg = kp->arg;
>
> ...
>
> if (multipath_head_always && !*kp->arg) {
> pr_err("Can't disable multipath when multipath_head_always is configured.\n");
> *arg = true;
>
>> +static int multipath_head_always_set(const char *val,
>> + const struct kernel_param *kp)
>> +{
>> + int ret;
>> +
>> + ret = param_set_bool(val, kp);
>> + if (ret < 0)
>> + return ret;
>> +
>> + if (*(bool *)kp->arg)
>> + multipath = true;
>
> Same here.
>
Agreed, will change in the next patch.
Thanks,
--Nilay
next prev parent reply other threads:[~2025-04-29 6:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 10:33 [RFC PATCHv2 0/3] improve NVMe multipath handling Nilay Shroff
2025-04-25 10:33 ` [RFC PATCHv2 1/3] nvme-multipath: introduce delayed removal of the multipath head node Nilay Shroff
2025-04-25 14:43 ` Christoph Hellwig
2025-04-28 7:05 ` Nilay Shroff
2025-04-25 22:26 ` Sagi Grimberg
2025-04-28 7:39 ` Nilay Shroff
2025-04-25 10:33 ` [RFC PATCHv2 2/3] nvme: introduce multipath_head_always module param Nilay Shroff
2025-04-25 14:45 ` Christoph Hellwig
2025-04-29 6:26 ` Nilay Shroff [this message]
2025-04-28 6:57 ` Hannes Reinecke
2025-04-28 7:39 ` Nilay Shroff
2025-04-29 5:49 ` Hannes Reinecke
2025-04-29 6:24 ` Nilay Shroff
2025-04-29 7:01 ` Hannes Reinecke
2025-04-29 7:15 ` Nilay Shroff
2025-04-25 10:33 ` [RFC PATCHv2 3/3] nvme: rename nvme_mpath_shutdown_disk to nvme_mpath_remove_disk Nilay Shroff
2025-04-25 14:46 ` Christoph Hellwig
2025-04-25 22:27 ` Sagi Grimberg
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=9a4245ed-bd5d-4a42-b8ef-3d4e557c69c8@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=gjoyce@ibm.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jmeneghi@redhat.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=sagi@grimberg.me \
/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