From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme-rdma: rework queue maps handling
Date: Sat, 19 Jan 2019 14:22:22 +0100 [thread overview]
Message-ID: <20190119132222.GA24605@lst.de> (raw)
In-Reply-To: <20190119005406.12855-1-sagi@grimberg.me>
On Fri, Jan 18, 2019@04:54:06PM -0800, Sagi Grimberg wrote:
> If the device supports less queues than provided (if the device has less
> completion vectors), we might hit a bug due to the fact that we ignore
> that in nvme_rdma_map_queues (we override the maps nr_queues with user
> opts).
>
> Instead, keep track of how many default/read/poll queues we actually
> allocated (rather than asked by the user) and use that to assign our
> queue mappings.
>
> Fixes: b65bb777ef22 (" nvme-rdma: support separate queue maps for read and write")
> Reported-by: Saleem, Shiraz <shiraz.saleem at intel.com>
> Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
> ---
> drivers/nvme/host/rdma.c | 37 ++++++++++++++++++++++++-------------
> 1 file changed, 24 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/nvme/host/rdma.c b/drivers/nvme/host/rdma.c
> index 079d59c04a0e..24a5b6783f29 100644
> --- a/drivers/nvme/host/rdma.c
> +++ b/drivers/nvme/host/rdma.c
> @@ -119,6 +119,7 @@ struct nvme_rdma_ctrl {
>
> struct nvme_ctrl ctrl;
> bool use_inline_data;
> + u32 io_queues[HCTX_MAX_TYPES];
> };
>
> static inline struct nvme_rdma_ctrl *to_rdma_ctrl(struct nvme_ctrl *ctrl)
> @@ -165,8 +166,8 @@ static inline int nvme_rdma_queue_idx(struct nvme_rdma_queue *queue)
> static bool nvme_rdma_poll_queue(struct nvme_rdma_queue *queue)
> {
> return nvme_rdma_queue_idx(queue) >
> - queue->ctrl->ctrl.opts->nr_io_queues +
> - queue->ctrl->ctrl.opts->nr_write_queues;
> + queue->ctrl->io_queues[HCTX_TYPE_DEFAULT] +
> + queue->ctrl->io_queues[HCTX_TYPE_READ];
> }
>
> static inline size_t nvme_rdma_inline_data_size(struct nvme_rdma_queue *queue)
> @@ -661,8 +662,20 @@ static int nvme_rdma_alloc_io_queues(struct nvme_rdma_ctrl *ctrl)
> nr_io_queues = min_t(unsigned int, nr_io_queues,
> ibdev->num_comp_vectors);
>
> - nr_io_queues += min(opts->nr_write_queues, num_online_cpus());
> - nr_io_queues += min(opts->nr_poll_queues, num_online_cpus());
> + ctrl->io_queues[HCTX_TYPE_READ] = nr_io_queues;
> + if (opts->nr_write_queues) {
> + ctrl->io_queues[HCTX_TYPE_DEFAULT] =
> + min(opts->nr_write_queues, nr_io_queues);
> + nr_io_queues += ctrl->io_queues[HCTX_TYPE_DEFAULT];
> + } else {
> + ctrl->io_queues[HCTX_TYPE_DEFAULT] = nr_io_queues;
> + }
Nipick: I'd find this easier to read of the HCTX_TYPE_READ line was
after the default one (I know, this is purely cosmetics).
Otherwise looks fine:
Reviewed-by: Christoph Hellwig <hch at lst.de>
next prev parent reply other threads:[~2019-01-19 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 0:54 [PATCH] nvme-rdma: rework queue maps handling Sagi Grimberg
2019-01-19 13:22 ` Christoph Hellwig [this message]
2019-01-21 9:11 ` Sagi Grimberg
2019-01-23 15:00 ` Shiraz Saleem
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=20190119132222.GA24605@lst.de \
--to=hch@lst.de \
/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