From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Christoph Lameter <cl@linux.com>
Cc: Zhang Yanfei <zhangyanfei.yes@gmail.com>,
Minchan Kim <minchan@kernel.org>, Hui Zhu <teawater@gmail.com>,
akpm@linux-foundation.org, mgorman@suse.de, hannes@cmpxchg.org,
riel@redhat.com, vbabka@suse.cz, isimatu.yasuaki@jp.fujitsu.com,
wangnan0@huawei.com, davidlohr@hp.com, rientjes@google.com,
sasha.levin@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Hui Zhu <zhuhui@xiaomi.com>,
Weixing Liu <liuweixing@xiaomi.com>
Subject: Re: [PATCH] CMA: treat free cma pages as non-free if not ALLOC_CMA on watermark checking
Date: Fri, 23 Jan 2015 10:23:34 +0900 [thread overview]
Message-ID: <20150123012334.GA32632@js1304-P5Q-DELUXE> (raw)
In-Reply-To: <alpine.DEB.2.11.1501221012000.3937@gentwo.org>
On Thu, Jan 22, 2015 at 10:12:43AM -0600, Christoph Lameter wrote:
> On Thu, 22 Jan 2015, Joonsoo Kim wrote:
>
> > > Just out of curiosity, "new zone"? Something like movable zone?
> >
> > Yes, I named it as ZONE_CMA. Maybe I can send prototype of
> > implementation within 1 or 2 weeks.
>
> Ugghh. I'd rather reduce the zone types. Do we need slab allocator etc
> allocations in that zone? This will multiply the management structures in
> various subsystems.
Hello,
Pages in CMA area should be movable so slab allocator which uses
unmovable/reclaimable allocation wouldn't need to consider that zone.
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-23 1:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 8:32 Hui Zhu
2015-01-19 6:55 ` Minchan Kim
2015-01-19 7:37 ` Hui Zhu
2015-01-20 15:33 ` Zhang Yanfei
2015-01-22 1:57 ` Joonsoo Kim
2015-01-22 16:12 ` Christoph Lameter
2015-01-23 1:23 ` 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=20150123012334.GA32632@js1304-P5Q-DELUXE \
--to=iamjoonsoo.kim@lge.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=davidlohr@hp.com \
--cc=hannes@cmpxchg.org \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuweixing@xiaomi.com \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=sasha.levin@oracle.com \
--cc=teawater@gmail.com \
--cc=vbabka@suse.cz \
--cc=wangnan0@huawei.com \
--cc=zhangyanfei.yes@gmail.com \
--cc=zhuhui@xiaomi.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