From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Keith Busch <kbusch@kernel.org>
Cc: sagi@grimberg.me, linux-nvme@lists.infradead.org, hch@lst.de
Subject: Re: [PATCHv2] nvme: only use power of two io boundaries
Date: Thu, 27 Aug 2020 11:48:21 -0400 [thread overview]
Message-ID: <yq1bliwm72c.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20200827152824.2784396-1-kbusch@kernel.org> (Keith Busch's message of "Thu, 27 Aug 2020 08:28:24 -0700")
Keith,
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> index 154942fc64eb..9bbbd600621f 100644
> --- a/drivers/nvme/host/core.c
> +++ b/drivers/nvme/host/core.c
> @@ -2097,8 +2097,12 @@ static int __nvme_revalidate_disk(struct gendisk *disk, struct nvme_id_ns *id)
> }
> }
>
> - if (iob && !blk_queue_is_zoned(ns->queue))
> - blk_queue_chunk_sectors(ns->queue, rounddown_pow_of_two(iob));
> + if (is_power_of_2(iob) && !blk_queue_is_zoned(ns->queue))
> + blk_queue_chunk_sectors(ns->queue, iob);
> + else if (iob && !(disk->flags & GENHD_FL_UP))
> + dev_warn(ctrl->device, "namespace:%u has unused io boundary:%u\n",
You used "unusable" in the patch description above. Did you mean that
here too?
Maybe something like:
"namespace%u: ignoring unsupported I/O boundary:%u\n"
to make it clear that this is due to a kernel limitation and not the
drive reporting garbage.
> + ns->head->ns_id, iob);
> +
> nvme_update_disk_info(disk, ns, id);
> #ifdef CONFIG_NVME_MULTIPATH
> if (ns->head->disk) {
Otherwise OK.
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen Oracle Linux Engineering
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-08-27 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 15:28 [PATCHv2] nvme: only use power of two io boundaries Keith Busch
2020-08-27 15:48 ` Martin K. Petersen [this message]
2020-08-27 15:53 ` Keith Busch
2020-08-27 16:06 ` Christoph Hellwig
2020-08-27 16:44 ` Keith Busch
2020-08-27 16:50 ` Christoph Hellwig
2020-08-28 1:03 ` Damien Le Moal
2020-08-28 4:16 ` Keith Busch
2020-08-28 4:30 ` Damien Le Moal
2020-08-28 4:44 ` Keith Busch
2020-08-28 4:56 ` Damien Le Moal
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=yq1bliwm72c.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=hch@lst.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.