From: Chen Feng <puck.chen@hisilicon.com>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
<mgorman@techsingularity.net>,
"Laura Abbott" <lauraa@codeaurora.org>,
Minchan Kim <minchan@kernel.org>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
Michal Nazarewicz <mina86@mina86.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Vlastimil Babka <vbabka@suse.cz>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 2/6] mm/cma: introduce new zone, ZONE_CMA
Date: Mon, 7 Nov 2016 15:08:49 +0800 [thread overview]
Message-ID: <58202881.5030004@hisilicon.com> (raw)
In-Reply-To: <20161107061500.GA21159@js1304-P5Q-DELUXE>
On 2016/11/7 14:15, Joonsoo Kim wrote:
> On Tue, Nov 01, 2016 at 03:58:32PM +0800, Chen Feng wrote:
>> Hello, I hava a question on cma zone.
>>
>> When we have cma zone, cma zone will be the highest zone of system.
>>
>> In android system, the most memory allocator is ION. Media system will
>> alloc unmovable memory from it.
>>
>> On low memory scene, will the CMA zone always do balance?
>
> Allocation request for low zone (normal zone) would not cause CMA zone
> to be balanced since it isn't helpful.
>
Yes. But the cma zone will run out soon. And it always need to do balance.
How about use migrate cma before movable and let cma type to fallback movable.
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1263745.html
>> Should we transmit the highest available zone to kswapd？
>
> It is already done when necessary.
>
> Thanks.
>
>
> .
>
next prev parent reply other threads:[~2016-11-07 7:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 3:03 [PATCH v6 0/6] Introduce ZONE_CMA js1304
2016-10-14 3:03 ` [PATCH v6 1/6] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request js1304
2016-10-14 3:03 ` [PATCH v6 2/6] mm/cma: introduce new zone, ZONE_CMA js1304
2016-11-01 7:58 ` Chen Feng
2016-11-07 6:15 ` Joonsoo Kim
2016-11-07 7:08 ` Chen Feng [this message]
2016-11-07 7:27 ` Joonsoo Kim
2016-11-07 7:44 ` Chen Feng
2016-11-07 7:46 ` Chen Feng
2016-11-08 3:59 ` Joonsoo Kim
2016-11-08 6:59 ` Chen Feng
2016-11-11 6:38 ` Joonsoo Kim
2016-10-14 3:03 ` [PATCH v6 3/6] mm/cma: populate ZONE_CMA js1304
2016-10-18 7:42 ` Vlastimil Babka
2016-10-18 8:27 ` Joonsoo Kim
2016-10-26 4:31 ` Joonsoo Kim
2016-10-26 7:27 ` Vlastimil Babka
2016-10-14 3:03 ` [PATCH v6 4/6] mm/cma: remove ALLOC_CMA js1304
2016-10-14 3:03 ` [PATCH v6 5/6] mm/cma: remove MIGRATE_CMA js1304
2016-10-14 3:03 ` [PATCH v6 6/6] mm/cma: remove per zone CMA stat js1304
2016-11-07 6:25 ` [PATCH v6 0/6] Introduce ZONE_CMA Joonsoo Kim
2016-11-28 7:41 ` Joonsoo 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=58202881.5030004@hisilicon.com \
--to=puck.chen@hisilicon.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=lauraa@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mgorman@techsingularity.net \
--cc=mina86@mina86.com \
--cc=minchan@kernel.org \
--cc=riel@redhat.com \
--cc=vbabka@suse.cz \
/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).