From: Joonsoo Kim <js1304@gmail.com>
To: Heesub Shin <heesub.shin@samsung.com>
Cc: Jun Nie <jun.nie@linaro.org>, Arnd Bergmann <arnd@arndb.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Shawn Guo <shawn.guo@linaro.org>,
"mark.brown@linaro.org, wan.zhijun" <wan.zhijun@zte.com.cn>,
linux-arm-kernel@lists.infradead.org,
Linux Memory Management List <linux-mm@kvack.org>,
sunae.seo@samsung.com, cmlaika.kim@samsung.com
Subject: Re: CMA related memory questions
Date: Fri, 30 Jan 2015 21:58:48 +0900 [thread overview]
Message-ID: <CAAmzW4OfrKt0XK5bDO0TNR5Ofv=rLDkpS7HAOCk0NRV1WdOhNg@mail.gmail.com> (raw)
In-Reply-To: <54CAF9A4.1040606@samsung.com>
2015-01-30 12:25 GMT+09:00 Heesub Shin <heesub.shin@samsung.com>:
>
>
> On 01/30/2015 11:57 AM, Jun Nie wrote:
>>
>> On 2015年01月30日 10:36, Jun Nie wrote:
>>>
>>> Hi Marek & Arnd,
>>>
>>> Did you ever know issue that free CMA memory is high, but system is
>>> hungry for memory and page cache is very low? I am enabling CMA in
>>> Android on my board with 512MB memory and see FreeMem in /proc/meminfo
>>> increase a lot with CMA comparing the reservation solution on boot. But
>>> I find system is not borrowing memory from CMA pool when running 3dmark
>>> (high webkit workload at start). Because the FreeMem size is high, but
>>> cache size decreasing significantly to several MB during benchmark run,
>>> I suppose system is trying to reclaim memory from pagecache for new
>>> allocation. My question is that what API that page cache and webkit
>>> related functionality are using to allocate memory. Maybe page cache
>>> require memory that is not movable/reclaimable memory, where we may have
>>> optimization to go thru dma_alloc_xxx to borrow CMA memory? I suppose
>>> app level memory allocation shall be movable/reclaimable memory and can
>>> borrow from CMA pool, but not sure whether the flag match the
>>> movable/reclaimable memory and go thru the right path.
Hello,
Maybe, you experienced the problem what I tried to solve.
CMA freepage allocation logic in mainline doesn't work well now since
they are only allocated in fallback case. See below link for detailed
explanation.
https://lkml.org/lkml/2014/5/28/64
This problem can be solved by aggressive allocation approach in that link, but,
there are too many issues left in CMA. So, I'm trying to implement ZONE_CMA
now. Prototyping is nearly finished so I will send it soon.
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>
prev parent reply other threads:[~2015-01-30 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABymUCNMjM2KHXXB-LM=x+FTcJL6S5_jhG3GbP7VRi2vBoW49g@mail.gmail.com>
[not found] ` <CABymUCO+xaify95bUqfbCLsEjkLzEC0yT_fgkhV+qzC36JNgoA@mail.gmail.com>
[not found] ` <CABymUCPgEh93QsBtRyg0S+FyE0FHwjAF75qk+NWh5TS8ehWuew@mail.gmail.com>
[not found] ` <54CAF314.4070301@linaro.org>
2015-01-30 3:25 ` CMA related memory questions Heesub Shin
2015-01-30 3:43 ` Jun Nie
2015-01-30 5:14 ` Heesub Shin
2015-01-30 8:54 ` Vlastimil Babka
2015-01-30 10:06 ` Hui Zhu
2015-01-30 12:58 ` Joonsoo Kim [this message]
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='CAAmzW4OfrKt0XK5bDO0TNR5Ofv=rLDkpS7HAOCk0NRV1WdOhNg@mail.gmail.com' \
--to=js1304@gmail.com \
--cc=arnd@arndb.de \
--cc=cmlaika.kim@samsung.com \
--cc=heesub.shin@samsung.com \
--cc=jun.nie@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=shawn.guo@linaro.org \
--cc=sunae.seo@samsung.com \
--cc=wan.zhijun@zte.com.cn \
/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).