From: Michal Nazarewicz <mina86@mina86.com>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>, Gioh Kim <gioh.kim@lge.com>
Cc: "Marek Szyprowski" <m.szyprowski@samsung.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"Heesub Shin" <heesub.shin@samsung.com>,
"Mel Gorman" <mgorman@suse.de>,
"Johannes Weiner" <hannes@cmpxchg.org>, 이건호 <gunho.lee@lge.com>
Subject: Re: [RFC PATCH] arm: dma-mapping: fallback allocation for cma failure
Date: Tue, 20 May 2014 08:22:03 -1000 [thread overview]
Message-ID: <xa1t1tvo1fas.fsf@mina86.com> (raw)
In-Reply-To: <20140520065222.GB8315@js1304-P5Q-DELUXE>
[-- Attachment #1: Type: text/plain, Size: 2997 bytes --]
On Mon, May 19 2014, Joonsoo Kim wrote:
> On Tue, May 20, 2014 at 02:57:47PM +0900, Gioh Kim wrote:
>>
>> Thanks for your advise, Michal Nazarewicz.
>>
>> Having discuss with Joonsoo, I'm adding fallback allocation after __alloc_from_contiguous().
>> The fallback allocation works if CMA kernel options is turned on but CMA size is zero.
>
> Hello, Gioh.
>
> I also mentioned the case where devices have their specific cma_area.
> It means that this device needs memory with some contraint.
> Although I'm not familiar with DMA infrastructure, I think that
> we should handle this case.
>
> How about below patch?
>
> ------------>8----------------
> diff --git a/arch/arm/mm/dma-mapping.c b/arch/arm/mm/dma-mapping.c
> index 6b00be1..4023434 100644
> --- a/arch/arm/mm/dma-mapping.c
> +++ b/arch/arm/mm/dma-mapping.c
> @@ -379,7 +379,7 @@ static int __init atomic_pool_init(void)
> unsigned long *bitmap;
> struct page *page;
> struct page **pages;
> - void *ptr;
> + void *ptr = NULL;
> int bitmap_size = BITS_TO_LONGS(nr_pages) * sizeof(long);
>
> bitmap = kzalloc(bitmap_size, GFP_KERNEL);
> @@ -393,7 +393,8 @@ static int __init atomic_pool_init(void)
> if (IS_ENABLED(CONFIG_DMA_CMA))
> ptr = __alloc_from_contiguous(NULL, pool->size, prot, &page,
> atomic_pool_init);
> - else
> +
> + if (!ptr)
> ptr = __alloc_remap_buffer(NULL, pool->size, gfp, prot, &page,
> atomic_pool_init);
> if (ptr) {
> @@ -701,10 +702,22 @@ static void *__dma_alloc(struct device *dev, size_t size, dma_addr_t *handle,
> addr = __alloc_simple_buffer(dev, size, gfp, &page);
> else if (!(gfp & __GFP_WAIT))
> addr = __alloc_from_pool(size, &page);
> - else if (!IS_ENABLED(CONFIG_DMA_CMA))
> - addr = __alloc_remap_buffer(dev, size, gfp, prot, &page, caller);
> - else
> - addr = __alloc_from_contiguous(dev, size, prot, &page, caller);
> + else {
> + if (IS_ENABLED(CONFIG_DMA_CMA)) {
> + addr = __alloc_from_contiguous(dev, size, prot,
> + &page, caller);
> + /*
> + * Device specific cma_area means that
> + * this device needs memory with some contraint.
> + * So, we can't fall through general remap allocation.
> + */
> + if (!addr && dev && dev->cma_area)
> + return NULL;
> + }
> +
> + addr = __alloc_remap_buffer(dev, size, gfp, prot,
> + &page, caller);
> + }
__arm_dma_free will have to be changed to handle the fallback as well.
But perhaps Marek is right and there should be no fallback for regular
allocations? Than again, non-CMA allocation should be performed at
least in the case of cma=0.
>
> if (addr)
> *handle = pfn_to_dma(dev, page_to_pfn(page));
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +--<mpn@google.com>--<xmpp:mina86@jabber.org>--ooO--(_)--Ooo--
[-- Attachment #2.1: Type: text/plain, Size: 0 bytes --]
[-- Attachment #2.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2014-05-20 18:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 5:57 [RFC PATCH] arm: dma-mapping: fallback allocation for cma failure Gioh Kim
2014-05-20 5:57 ` Gioh Kim
2014-05-20 6:52 ` Joonsoo Kim
2014-05-20 6:52 ` Joonsoo Kim
2014-05-20 7:05 ` Gioh Kim
2014-05-20 7:05 ` Gioh Kim
2014-05-20 8:32 ` Joonsoo Kim
2014-05-20 8:32 ` Joonsoo Kim
2014-05-20 23:39 ` Gioh Kim
2014-05-20 23:39 ` Gioh Kim
2014-05-20 18:22 ` Michal Nazarewicz [this message]
2014-05-21 0:24 ` Gioh Kim
2014-05-21 0:24 ` Gioh Kim
2014-05-21 8:06 ` Gioh Kim
2014-05-21 8:06 ` Gioh Kim
2014-05-21 20:11 ` Michal Nazarewicz
2014-05-21 20:11 ` Michal Nazarewicz
2014-05-22 1:02 ` Gioh Kim
2014-05-22 1:02 ` Gioh Kim
2014-05-22 3:22 ` Michal Nazarewicz
2014-05-22 3:22 ` Michal Nazarewicz
2014-05-22 4:30 ` Gioh Kim
2014-05-22 4:30 ` Gioh Kim
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=xa1t1tvo1fas.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=gioh.kim@lge.com \
--cc=gunho.lee@lge.com \
--cc=hannes@cmpxchg.org \
--cc=heesub.shin@samsung.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mgorman@suse.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 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.