linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Gioh Kim <gioh.kim@lge.com>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: "Marek Szyprowski" <m.szyprowski@samsung.com>,
	"Michal Nazarewicz" <mina86@mina86.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: Wed, 21 May 2014 08:39:54 +0900	[thread overview]
Message-ID: <537BE7CA.4030706@lge.com> (raw)
In-Reply-To: <20140520083206.GA8927@js1304-P5Q-DELUXE>



2014-05-20 i??i?? 5:32, Joonsoo Kim i?' e,?:
> On Tue, May 20, 2014 at 04:05:52PM +0900, Gioh Kim wrote:
>> That case, device-specific coherent memory allocation, is handled at dma_alloc_coherent in arm_dma_alloc.
>> __dma_alloc handles only general coherent memory allocation.
>>
>> I'm sorry missing mention about it.
>>
>
> Hello,
>
> AFAIK, *coherent* memory allocation is different with *contiguous* memory
> allocation(CMA). So we need to handle the case I mentioned.

Yes, I confused the coherent memory aand contiguous memory. It's my mistake.

So I checked dma_alloc_from_contiguous and found dev_get_cma_area function.
The dev_get_cma_area returns device-specific cma if it exists or default global-cma.
I think __alloc_from_contiguous doesn't distinguish device-specific cma area and global cma.
The purpose of __alloc_from_contiguous is allocation of contiguous memory from any cma area, not device-specific area.

If my assumption is right, __alloc_from_contiguous can be replaced with __alloc_remap_buffer without checking device-specific cma area.

What do you think about it?

>
> Thanks.
>

--
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>

  reply	other threads:[~2014-05-20 23:39 UTC|newest]

Thread overview: 12+ 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  6:52 ` Joonsoo Kim
2014-05-20  7:05   ` Gioh Kim
2014-05-20  8:32     ` Joonsoo Kim
2014-05-20 23:39       ` Gioh Kim [this message]
2014-05-20 18:22   ` Michal Nazarewicz
2014-05-21  0:24     ` Gioh Kim
2014-05-21  8:06     ` Gioh Kim
2014-05-21 20:11       ` Michal Nazarewicz
2014-05-22  1:02         ` Gioh Kim
2014-05-22  3:22           ` Michal Nazarewicz
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=537BE7CA.4030706@lge.com \
    --to=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 \
    --cc=mina86@mina86.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).