From: Michal Hocko <mhocko@kernel.org>
To: Laura Abbott <labbott@redhat.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC] CMA and larger page sizes
Date: Tue, 17 Apr 2018 13:36:56 +0200 [thread overview]
Message-ID: <20180417113656.GA16083@dhcp22.suse.cz> (raw)
In-Reply-To: <3a3d724e-4d74-9bd8-60f3-f6896cffac7a@redhat.com>
On Fri 26-01-18 02:08:14, Laura Abbott wrote:
> CMA as it's currently designed requires alignment to the pageblock size c.f.
>
> /*
> * Sanitise input arguments.
> * Pages both ends in CMA area could be merged into adjacent unmovable
> * migratetype page by page allocator's buddy algorithm. In the case,
> * you couldn't get a contiguous memory, which is not what we want.
> */
> alignment = max(alignment, (phys_addr_t)PAGE_SIZE <<
> max_t(unsigned long, MAX_ORDER - 1, pageblock_order));
>
>
> On arm64 with 64K page size and transparent huge page, this gives an alignment
> of 512MB. This is quite restrictive and can eat up significant portions of
> memory on smaller memory targets. Adjusting the configuration options really
> isn't ideal for distributions that aim to have a single image which runs on
> all targets.
>
> Approaches I've thought about:
> - Making CMA alignment less restrictive (and dealing with the fallout from
> the comment above)
> - Command line option to force a reasonable alignment
Laura, are you still interested discussing this or other CMA related
topic?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-04-17 11:36 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
2018-04-12 5:51 ` Michal Hocko
2018-04-12 6:27 ` Vlastimil Babka
2018-04-17 11:36 ` Michal Hocko [this message]
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=20180417113656.GA16083@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=labbott@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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