public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Liu Song <liusong@linux.alibaba.com>
To: Guixin Liu <kanie@linux.alibaba.com>,
	kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH V3] nvme: introduce nvme_disk_is_ns_head helper
Date: Thu, 28 Dec 2023 09:48:37 +0800	[thread overview]
Message-ID: <8e0b0055-0da9-4d23-b63e-09ca21f1b3e8@linux.alibaba.com> (raw)
In-Reply-To: <20231227093106.78551-1-kanie@linux.alibaba.com>

Using helper functions makes the code more readable.

Reviewed-by: Liu Song <liusong@linux.alibaba.com>

在 2023/12/27 17:31, Guixin Liu 写道:
> We currently rely on gendisk's file operations (fops) to distinguish
> between a namespace head (ns_head) and a regular namespace. To enhance
> code readability, introduce a helper function.
> Additionally, we must ensure that the device is not an ns_head before
> calling nvme_get_ns_from_dev(). To enforce this, add a WARN_ON check
> within the nvme_get_ns_from_dev().
>
> Signed-off-by: Guixin Liu <kanie@linux.alibaba.com>
> ---
> Changes from v2 to v3:
> - simplify to disk->fops == &nvme_ns_head_ops.
>
> Changes from v1 to v2:
> - change helper name from nvme_gendisk_is_ns_head to
>    nvme_disk_is_ns_head.
> - remove redundant comment.
>
>   drivers/nvme/host/nvme.h  | 10 +++++++++-
>   drivers/nvme/host/pr.c    |  2 +-
>   drivers/nvme/host/sysfs.c |  9 +++++----
>   3 files changed, 15 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/nvme/host/nvme.h b/drivers/nvme/host/nvme.h
> index e7411dac00f7..3dcbf48e9fdf 100644
> --- a/drivers/nvme/host/nvme.h
> +++ b/drivers/nvme/host/nvme.h
> @@ -1029,9 +1029,17 @@ static inline int nvme_update_zone_info(struct nvme_ns *ns, unsigned lbaf)
>   }
>   #endif
>   
> +static inline bool nvme_disk_is_ns_head(struct gendisk *disk)
> +{
> +	return disk->fops == &nvme_ns_head_ops;
> +}
> +
>   static inline struct nvme_ns *nvme_get_ns_from_dev(struct device *dev)
>   {
> -	return dev_to_disk(dev)->private_data;
> +	struct gendisk *disk = dev_to_disk(dev);
> +
> +	WARN_ON(nvme_disk_is_ns_head(disk));
> +	return disk->private_data;
>   }
>   
>   #ifdef CONFIG_NVME_HWMON
> diff --git a/drivers/nvme/host/pr.c b/drivers/nvme/host/pr.c
> index 391b1465ebfd..fc3eed00f9ff 100644
> --- a/drivers/nvme/host/pr.c
> +++ b/drivers/nvme/host/pr.c
> @@ -98,7 +98,7 @@ static int nvme_send_pr_command(struct block_device *bdev,
>   		struct nvme_command *c, void *data, unsigned int data_len)
>   {
>   	if (IS_ENABLED(CONFIG_NVME_MULTIPATH) &&
> -	    bdev->bd_disk->fops == &nvme_ns_head_ops)
> +	    nvme_disk_is_ns_head(bdev->bd_disk))
>   		return nvme_send_ns_head_pr_command(bdev, c, data, data_len);
>   
>   	return nvme_send_ns_pr_command(bdev->bd_disk->private_data, c, data,
> diff --git a/drivers/nvme/host/sysfs.c b/drivers/nvme/host/sysfs.c
> index c6b7fbd4d34d..925042ca728b 100644
> --- a/drivers/nvme/host/sysfs.c
> +++ b/drivers/nvme/host/sysfs.c
> @@ -39,10 +39,10 @@ static inline struct nvme_ns_head *dev_to_ns_head(struct device *dev)
>   {
>   	struct gendisk *disk = dev_to_disk(dev);
>   
> -	if (disk->fops == &nvme_bdev_ops)
> -		return nvme_get_ns_from_dev(dev)->head;
> -	else
> +	if (nvme_disk_is_ns_head(disk))
>   		return disk->private_data;
> +	else
> +		return nvme_get_ns_from_dev(dev)->head;
>   }
>   
>   static ssize_t wwid_show(struct device *dev, struct device_attribute *attr,
> @@ -148,7 +148,8 @@ static umode_t nvme_ns_id_attrs_are_visible(struct kobject *kobj,
>   	}
>   #ifdef CONFIG_NVME_MULTIPATH
>   	if (a == &dev_attr_ana_grpid.attr || a == &dev_attr_ana_state.attr) {
> -		if (dev_to_disk(dev)->fops != &nvme_bdev_ops) /* per-path attr */
> +		/* per-path attr */
> +		if (nvme_disk_is_ns_head(dev_to_disk(dev)))
>   			return 0;
>   		if (!nvme_ctrl_use_ana(nvme_get_ns_from_dev(dev)->ctrl))
>   			return 0;


  reply	other threads:[~2023-12-28  1:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-27  9:31 [PATCH V3] nvme: introduce nvme_disk_is_ns_head helper Guixin Liu
2023-12-28  1:48 ` Liu Song [this message]
2023-12-28  6:17 ` Christoph Hellwig
2024-01-01  9:49 ` Sagi Grimberg
2024-01-02 21:05 ` Keith Busch
2024-01-03 16:18   ` Keith Busch

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=8e0b0055-0da9-4d23-b63e-09ca21f1b3e8@linux.alibaba.com \
    --to=liusong@linux.alibaba.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kanie@linux.alibaba.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --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