From: David Hildenbrand <david@redhat.com>
To: Zi Yan <ziy@nvidia.com>, Juan Yescas <jyescas@google.com>
Cc: Barry Song <21cnbao@gmail.com>,
linux-mm@kvack.org, muchun.song@linux.dev, rppt@kernel.org,
osalvador@suse.de, akpm@linux-foundation.org,
lorenzo.stoakes@oracle.com, Jann Horn <jannh@google.com>,
Liam.Howlett@oracle.com, minchan@kernel.org,
jaewon31.kim@samsung.com, charante@codeaurora.org,
Suren Baghdasaryan <surenb@google.com>,
Kalesh Singh <kaleshsingh@google.com>,
"T.J. Mercier" <tjmercier@google.com>,
Isaac Manjarres <isaacmanjarres@google.com>,
iamjoonsoo.kim@lge.com, quic_charante@quicinc.com
Subject: Re: mm: CMA reservations require 32MiB alignment in 16KiB page size kernels instead of 8MiB in 4KiB page size kernel.
Date: Wed, 22 Jan 2025 14:58:03 +0100 [thread overview]
Message-ID: <5be3ed89-f19e-4f54-9e4e-fc8f39046b84@redhat.com> (raw)
In-Reply-To: <D78M4QZP8MSU.3DQ1YR81U2EFS@nvidia.com>
>> In the future, I could imagine just going for a smaller pageblock size
>> on aarch64, and handling fragmentation avoidance for larger THPs (512
>> MiB really is close to 1 GiB on x86) differently, not using pageblocks.
>
> Right. That is what I meant by "...compaction, to work on a different
> range, independent of pageblock". But based on Juan's reply[1], 32MB PMD
> THP is still needed for the deployment. That means "the future" needs to
> be done to fully satisfy Juan's needs. :)
Yes, larger systems will also want 512 MiB THP.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-01-22 13:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 22:51 Juan Yescas
2025-01-17 22:52 ` Juan Yescas
2025-01-17 23:00 ` Juan Yescas
2025-01-17 23:19 ` Zi Yan
2025-01-19 23:55 ` Barry Song
2025-01-20 0:39 ` Zi Yan
2025-01-20 8:14 ` David Hildenbrand
2025-01-20 15:29 ` Zi Yan
2025-01-20 17:59 ` David Hildenbrand
2025-01-22 2:08 ` Juan Yescas
2025-01-22 2:24 ` Zi Yan
2025-01-22 4:06 ` Juan Yescas
2025-01-22 6:52 ` Barry Song
2025-01-22 8:04 ` David Hildenbrand
2025-01-22 8:11 ` David Hildenbrand
2025-01-22 12:49 ` Zi Yan
2025-01-22 13:58 ` David Hildenbrand [this message]
2025-01-20 0:17 ` Barry Song
2025-01-20 0:26 ` Zi Yan
2025-01-20 0:38 ` Barry Song
2025-01-20 0:45 ` Zi Yan
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=5be3ed89-f19e-4f54-9e4e-fc8f39046b84@redhat.com \
--to=david@redhat.com \
--cc=21cnbao@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=charante@codeaurora.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=isaacmanjarres@google.com \
--cc=jaewon31.kim@samsung.com \
--cc=jannh@google.com \
--cc=jyescas@google.com \
--cc=kaleshsingh@google.com \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=minchan@kernel.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=quic_charante@quicinc.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=tjmercier@google.com \
--cc=ziy@nvidia.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