From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: chris@zankel.net, linux-xtensa@linux-xtensa.org,
dwmw2@infradead.org, joro@8bytes.org, will.deacon@arm.com,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
jonathanh@nvidia.com, jcmvbkbc@gmail.com, robin.murphy@arm.com,
hch@lst.de, linux-arm-kernel@lists.infradead.org,
m.szyprowski@samsung.com
Subject: Re: [PATCH v2 RFC/RFT] dma-contiguous: Get normal pages for single-page allocations
Date: Fri, 22 Mar 2019 13:09:26 -0700 [thread overview]
Message-ID: <20190322200925.GA22219@Asurada-Nvidia> (raw)
In-Reply-To: <20190322105712.GB13384@arrakis.emea.arm.com>
Hi Catalin,
On Fri, Mar 22, 2019 at 10:57:13AM +0000, Catalin Marinas wrote:
> > > Do you have any numbers to back this up? You don't seem to address
> > > dma_direct_alloc() either but, as I said above, it's not trivial since
> > > some platforms expect certain physical range for DMA allocations.
> >
> > What's the dma_direct_alloc() here about? Mind elaborating?
>
> I just did a grep for dma_alloc_from_contiguous() in the 5.1-rc1 kernel
> and came up with __dma_direct_alloc_pages(). Should your patch cover
> this as well?
I don't get the meaning of "cover this" here. What missing part
do you refer to?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-22 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 18:32 [PATCH v2 RFC/RFT] dma-contiguous: Get normal pages for single-page allocations Nicolin Chen
2019-03-19 14:43 ` Catalin Marinas
2019-03-21 23:32 ` Nicolin Chen
2019-03-22 10:57 ` Catalin Marinas
2019-03-22 20:09 ` Nicolin Chen [this message]
2019-03-25 12:14 ` Catalin Marinas
2019-03-25 18:50 ` Nicolin Chen
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=20190322200925.GA22219@Asurada-Nvidia \
--to=nicoleotsuka@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=chris@zankel.net \
--cc=dwmw2@infradead.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=jcmvbkbc@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=will.deacon@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).