From: Dave Jiang <dave.jiang@intel.com>
To: Logan Gunthorpe <logang@deltatee.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Robin Murphy <robin.murphy@arm.com>,
Vinod Koul <vkoul@kernel.org>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] dmaengine: ioat: Allocate correct size for descriptor chunk
Date: Tue, 22 Sep 2020 13:18:13 -0700 [thread overview]
Message-ID: <a8dacb00-ae27-f5d1-c8f7-5c06853e8b69@intel.com> (raw)
In-Reply-To: <20200922200844.2982-1-logang@deltatee.com>
On 9/22/2020 1:08 PM, Logan Gunthorpe wrote:
> dma_alloc_coherent() is called with a fixed SZ_2M size, but frees happen
> with IOAT_CHUNK_SIZE. Recently, IOAT_CHUNK_SIZE was reduced to 512M but
> the allocation did not change. To fix, change to using the
> IOAT_CHUNK_SIZE define.
>
> This was caught with the upcoming patchset for converting Intel platforms to the
> dma-iommu implementation. It has a warning when the unmapped size differs from
> the mapped size.
>
> Fixes: a02254f8a676 ("dmaengine: ioat: Decreasing allocation chunk size 2M->512K")
> Link: https://lore.kernel.org/intel-gfx/776771a2-247a-d1be-d882-bee02d919ae0@deltatee.com/
> Suggested-by: Robin Murphy <robin.murphy@arm.com>
> Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
> Cc: Vinod Koul <vkoul@kernel.org>
> Cc: Dave Jiang <dave.jiang@intel.com>
> Cc: Dan Williams <dan.j.williams@intel.com>
Acked-by: Dave Jiang <dave.jiang@intel.com>
Thanks Logan.
> ---
> drivers/dma/ioat/dma.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma/ioat/dma.c b/drivers/dma/ioat/dma.c
> index a814b200299b..07296171e2bb 100644
> --- a/drivers/dma/ioat/dma.c
> +++ b/drivers/dma/ioat/dma.c
> @@ -389,7 +389,7 @@ ioat_alloc_ring(struct dma_chan *c, int order, gfp_t flags)
> struct ioat_descs *descs = &ioat_chan->descs[i];
>
> descs->virt = dma_alloc_coherent(to_dev(ioat_chan),
> - SZ_2M, &descs->hw, flags);
> + IOAT_CHUNK_SIZE, &descs->hw, flags);
> if (!descs->virt) {
> int idx;
>
>
> base-commit: ba4f184e126b751d1bffad5897f263108befc780
>
next prev parent reply other threads:[~2020-09-22 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 20:08 [PATCH] dmaengine: ioat: Allocate correct size for descriptor chunk Logan Gunthorpe
2020-09-22 20:18 ` Dave Jiang [this message]
2020-10-05 4:46 ` Vinod Koul
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=a8dacb00-ae27-f5d1-c8f7-5c06853e8b69@intel.com \
--to=dave.jiang@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=robin.murphy@arm.com \
--cc=vkoul@kernel.org \
/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