From: Michal Nazarewicz <mina86@mina86.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org,
linaro-mm-sig@lists.linaro.org
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] ARM: mm: don't limit default CMA region only to low memory
Date: Sun, 24 Aug 2014 15:34:36 +0200 [thread overview]
Message-ID: <xa1tvbpiui37.fsf@mina86.com> (raw)
In-Reply-To: <1408610714-16204-3-git-send-email-m.szyprowski@samsung.com>
On Thu, Aug 21 2014, Marek Szyprowski <m.szyprowski@samsung.com> wrote:
> DMA-mapping supports CMA regions places either in low or high memory, so
> there is no longer needed to limit default CMA regions only to low memory.
> The real limit is still defined by architecture specific DMA limit.
>
> Reported-by: Russell King - ARM Linux <linux@arm.linux.org.uk>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Acked-by: Michal Nazarewicz <mina86@mina86.com>
> ---
> arch/arm/mm/init.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/mm/init.c b/arch/arm/mm/init.c
> index 659c75d808dc..c1b513555786 100644
> --- a/arch/arm/mm/init.c
> +++ b/arch/arm/mm/init.c
> @@ -322,7 +322,7 @@ void __init arm_memblock_init(const struct machine_desc *mdesc)
> * reserve memory for DMA contigouos allocations,
> * must come from DMA area inside low memory
> */
> - dma_contiguous_reserve(min(arm_dma_limit, arm_lowmem_limit));
> + dma_contiguous_reserve(arm_dma_limit);
>
> arm_memblock_steal_permitted = false;
> memblock_dump_all();
> --
> 1.9.2
>
--
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--
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-08-24 13:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 8:45 [PATCH 0/2] ARM: Remove lowmem limit for default CMA region Marek Szyprowski
2014-08-21 8:45 ` [PATCH 1/2] mm: cma: adjust address limit to avoid hitting low/high memory boundary Marek Szyprowski
2014-08-24 13:34 ` Michal Nazarewicz
2014-08-21 8:45 ` [PATCH 2/2] ARM: mm: don't limit default CMA region only to low memory Marek Szyprowski
2014-08-21 9:26 ` Daniel Drake
2014-08-24 13:34 ` Michal Nazarewicz [this message]
2014-08-25 1:26 ` [PATCH 0/2] ARM: Remove lowmem limit for default CMA region Minchan Kim
2014-08-25 8:00 ` Marek Szyprowski
2014-08-25 8:18 ` Minchan Kim
2014-08-25 8:33 ` Marek Szyprowski
2014-08-26 2:43 ` Minchan Kim
2014-08-26 12:34 ` Marek Szyprowski
2014-08-27 0:36 ` Minchan Kim
2014-08-27 1:42 ` Joonsoo Kim
2014-08-27 2:57 ` Minchan Kim
2014-08-26 23:10 ` Andrew Morton
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=xa1tvbpiui37.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=m.szyprowski@samsung.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