From: Aaron Williams <awilliams@marvell.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] nvme: Fix PRP Offset Invalid
Date: Thu, 22 Aug 2019 09:17:26 +0000 [thread overview]
Message-ID: <62686292.IhoNlLAHOO@flash> (raw)
In-Reply-To: <20190822091232.13331-1-awilliams@marvell.com>
I'm sorry about the messed up subject saying [PATCH]. For some reason git
send-email is mangling the subject line. I'm new to trying to use this method
to send out patches. This is version 2 of my patch.
-Aaron
On Thursday, August 22, 2019 2:12:32 AM PDT Aaron Williams wrote:
> When large writes take place I saw a Samsung EVO 970+ return a status
> value of 0x13, PRP Offset Invalid. I tracked this down to the
> improper handling of PRP entries. The blocks the PRP entries are
> placed in cannot cross a page boundary and thus should be allocated
> on page boundaries. This is how the Linux kernel driver works.
>
> With this patch, the PRP pool is allocated on a page boundary and
> other than the very first allocation, the pool size is a multiple of
> the page size. Each page can hold (4096 / 8) - 1 entries since the
> last entry must point to the next page in the pool.
>
> Signed-off-by: Aaron Williams <awilliams@marvell.com>
> ---
> drivers/nvme/nvme.c | 28 ++++++++++++++++++----------
> 1 file changed, 18 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/nvme/nvme.c b/drivers/nvme/nvme.c
> index d4965e2ef6..bc4cf40b40 100644
> --- a/drivers/nvme/nvme.c
> +++ b/drivers/nvme/nvme.c
> @@ -73,6 +73,9 @@ static int nvme_setup_prps(struct nvme_dev *dev, u64
> *prp2, u64 *prp_pool;
> int length = total_len;
> int i, nprps;
> + u32 prps_per_page = (page_size >> 3) - 1;
> + u32 num_pages;
> +
> length -= (page_size - offset);
>
> if (length <= 0) {
> @@ -89,15 +92,19 @@ static int nvme_setup_prps(struct nvme_dev *dev, u64
> *prp2, }
>
> nprps = DIV_ROUND_UP(length, page_size);
> + num_pages = DIV_ROUND_UP(nprps, prps_per_page);
>
> if (nprps > dev->prp_entry_num) {
> free(dev->prp_pool);
> - dev->prp_pool = malloc(nprps << 3);
> + /* Always increase in increments of pages. It doesn't
waste
> + * much memory and reduces the number of allocations.
> + */
> + dev->prp_pool = memalign(page_size, num_pages *
page_size);
> if (!dev->prp_pool) {
> printf("Error: malloc prp_pool fail\n");
> return -ENOMEM;
> }
> - dev->prp_entry_num = nprps;
> + dev->prp_entry_num = prps_per_page * num_pages;
> }
>
> prp_pool = dev->prp_pool;
> @@ -788,14 +795,6 @@ static int nvme_probe(struct udevice *udev)
> }
> memset(ndev->queues, 0, NVME_Q_NUM * sizeof(struct nvme_queue
*));
>
> - ndev->prp_pool = malloc(MAX_PRP_POOL);
> - if (!ndev->prp_pool) {
> - ret = -ENOMEM;
> - printf("Error: %s: Out of memory!\n", udev->name);
> - goto free_nvme;
> - }
> - ndev->prp_entry_num = MAX_PRP_POOL >> 3;
> -
> ndev->cap = nvme_readq(&ndev->bar->cap);
> ndev->q_depth = min_t(int, NVME_CAP_MQES(ndev->cap) + 1,
NVME_Q_DEPTH);
> ndev->db_stride = 1 << NVME_CAP_STRIDE(ndev->cap);
> @@ -805,6 +804,15 @@ static int nvme_probe(struct udevice *udev)
> if (ret)
> goto free_queue;
>
> + /* Allocate after the page size is known */
> + ndev->prp_pool = memalign(ndev->page_size, MAX_PRP_POOL);
> + if (!ndev->prp_pool) {
> + ret = -ENOMEM;
> + printf("Error: %s: Out of memory!\n", udev->name);
> + goto free_nvme;
> + }
> + ndev->prp_entry_num = MAX_PRP_POOL >> 3;
> +
> ret = nvme_setup_io_queues(ndev);
> if (ret)
> goto free_queue;
next prev parent reply other threads:[~2019-08-22 9:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 0:34 [U-Boot] [PATCH 1/1] nvme: Fix PRP Offset Invalid Aaron Williams
2019-08-21 7:55 ` Bin Meng
2019-08-21 11:23 ` [U-Boot] [PATCH 1/1][nvme] " Aaron Williams
2019-08-21 11:23 ` [U-Boot] [PATCH] nvme: " Aaron Williams
2019-08-21 11:26 ` [U-Boot] [EXT] Re: [PATCH 1/1] " Aaron Williams
2019-08-21 15:23 ` Bin Meng
2019-08-21 22:06 ` Aaron Williams
2019-08-22 1:38 ` Bin Meng
2019-08-22 9:12 ` [U-Boot] [PATCH] " Aaron Williams
2019-08-22 9:17 ` Aaron Williams [this message]
2019-08-22 14:25 ` Bin Meng
2019-08-22 18:05 ` [U-Boot] [PATCH v3 1/1] " Aaron Williams
2019-08-22 18:05 ` [U-Boot] [PATCH v3 0/1] nvme: Fix invalid PRP Offset Aaron Williams
2019-08-22 18:05 ` [U-Boot] [PATCH v3 1/1] nvme: Fix PRP Offset Invalid Aaron Williams
2019-08-23 3:24 ` Bin Meng
2019-08-23 3:37 ` [U-Boot] [PATCH v4 " Aaron Williams
2019-08-23 3:37 ` [U-Boot] [PATCH v4 0/1] " Aaron Williams
2019-08-23 3:37 ` [U-Boot] [PATCH v4 1/1] " Aaron Williams
2019-08-27 0:19 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2019-08-21 14:09 [U-Boot] [PATCH] " Aaron Williams
2019-08-22 1:40 ` Bin Meng
2019-08-22 2:48 ` Aaron Williams
2019-08-21 13:40 Aaron Williams
2019-08-20 7:18 Aaron Williams
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=62686292.IhoNlLAHOO@flash \
--to=awilliams@marvell.com \
--cc=u-boot@lists.denx.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