From: Laura Abbott <labbott@redhat.com>
To: Vlastimil Babka <vbabka@suse.cz>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Michal Hocko <mhocko@kernel.org>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC] CMA and larger page sizes
Date: Wed, 11 Apr 2018 18:06:59 -0700 [thread overview]
Message-ID: <b1420dd8-23ae-89e8-3b9d-62663bd69e24@redhat.com> (raw)
In-Reply-To: <d88676d9-8f42-2519-56bf-776e46b1180e@suse.cz>
On 04/11/2018 01:02 PM, Vlastimil Babka wrote:
> On 04/11/2018 09:55 PM, Laura Abbott wrote:
>> On 04/03/2018 10:11 PM, Joonsoo Kim wrote:
>>> If the patchset 'manage the memory of the CMA area by using the ZONE_MOVABLE' is
>>> merged, this restriction can be removed since there is no unmovable
>>> pageblock in ZONE_MOVABLE. Just quick thought. :)
>>>
>>> Thanks.
>>>
>>
>> Thanks for that pointer. What's the current status of that patchset? Was that
>> one that needed more review/testing?
>
> It was merged by Linus today, see around commit bad8c6c0b114 ("mm/cma:
> manage the memory of the CMA area by using the ZONE_MOVABLE")
>
> Congrats, Joonsoo :)
>
I took a look at this a little bit more and while it's true we don't
have the unmovable restriction anymore, CMA is still tied to the pageblock
size (512MB) because we still have MIGRATE_CMA. I guess making the
pageblock smaller seems like the most plausible approach?
Thanks,
Laura
next prev parent reply other threads:[~2018-04-12 1:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 10:08 Laura Abbott
2018-01-26 17:25 ` Michal Hocko
2018-04-04 5:11 ` Joonsoo Kim
2018-04-11 19:55 ` Laura Abbott
2018-04-11 20:02 ` Vlastimil Babka
2018-04-12 1:06 ` Laura Abbott [this message]
2018-04-12 5:51 ` Michal Hocko
2018-04-12 6:27 ` Vlastimil Babka
2018-04-17 11:36 ` Michal Hocko
2018-04-17 15:01 ` Laura Abbott
2018-04-18 8:17 ` Michal Hocko
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=b1420dd8-23ae-89e8-3b9d-62663bd69e24@redhat.com \
--to=labbott@redhat.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mhocko@kernel.org \
--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