From: Oscar Salvador <osalvador@suse.de>
To: David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Mike Rapoport <rppt@kernel.org>, Michal Hocko <mhocko@kernel.org>,
Wei Yang <richard.weiyang@linux.alibaba.com>
Subject: Re: [PATCH v1 1/2] mm/cma: expose all pages to the buddy if activation of an area fails
Date: Thu, 28 Jan 2021 10:59:06 +0100 [thread overview]
Message-ID: <20210128095906.GA5250@localhost.localdomain> (raw)
In-Reply-To: <20210127101813.6370-2-david@redhat.com>
On Wed, Jan 27, 2021 at 11:18:12AM +0100, David Hildenbrand wrote:
> Right now, if activation fails, we might already have exposed some pages to
> the buddy for CMA use (although they will never get actually used by CMA),
> and some pages won't be exposed to the buddy at all.
>
> Let's check for "single zone" early and on error, don't expose any pages
> for CMA use - instead, expose them to the buddy available for any use.
> Simply call free_reserved_page() on every single page - easier than
> going via free_reserved_area(), converting back and forth between pfns
> and virt addresses.
>
> In addition, make sure to fixup totalcma_pages properly.
>
> Example: 6 GiB QEMU VM with "... hugetlb_cma=2G movablecore=20% ...":
> [ 0.006891] hugetlb_cma: reserve 2048 MiB, up to 2048 MiB per node
> [ 0.006893] cma: Reserved 2048 MiB at 0x0000000100000000
> [ 0.006893] hugetlb_cma: reserved 2048 MiB on node 0
> ...
> [ 0.175433] cma: CMA area hugetlb0 could not be activated
>
> Before this patch:
> # cat /proc/meminfo
> MemTotal: 5867348 kB
> MemFree: 5692808 kB
> MemAvailable: 5542516 kB
> ...
> CmaTotal: 2097152 kB
> CmaFree: 1884160 kB
>
> After this patch:
> # cat /proc/meminfo
> MemTotal: 6077308 kB
> MemFree: 5904208 kB
> MemAvailable: 5747968 kB
> ...
> CmaTotal: 0 kB
> CmaFree: 0 kB
>
> Note: cma_init_reserved_mem() makes sure that we always cover full
> pageblocks / MAX_ORDER - 1 pages.
>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: "Peter Zijlstra (Intel)" <peterz@infradead.org>
> Cc: Mike Rapoport <rppt@kernel.org>
> Cc: Oscar Salvador <osalvador@suse.de>
> Cc: Michal Hocko <mhocko@kernel.org>
> Cc: Wei Yang <richard.weiyang@linux.alibaba.com>
> Signed-off-by: David Hildenbrand <david@redhat.com>
Besides benefit of the error handling, I find this code much more
cleaer:
Reviewed-by: Oscar Salvador <osalvador@suse.de>
--
Oscar Salvador
SUSE L3
next prev parent reply other threads:[~2021-01-28 9:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 10:18 [PATCH v1 0/2] mm/cma: better error handling and count pages per zone David Hildenbrand
2021-01-27 10:18 ` [PATCH v1 1/2] mm/cma: expose all pages to the buddy if activation of an area fails David Hildenbrand
2021-01-27 15:58 ` Zi Yan
2021-01-28 9:59 ` Oscar Salvador [this message]
2021-01-27 10:18 ` [PATCH v1 2/2] mm/page_alloc: count CMA pages per zone and print them in /proc/zoneinfo David Hildenbrand
2021-01-28 10:22 ` Oscar Salvador
2021-01-28 10:43 ` David Hildenbrand
2021-01-28 13:44 ` Oscar Salvador
2021-01-28 13:46 ` Oscar Salvador
2021-01-28 14:01 ` David Hildenbrand
2021-01-28 16:45 ` [PATCH v2] " David Hildenbrand
2021-01-28 21:42 ` Oscar Salvador
2021-01-28 21:54 ` David Rientjes
2021-01-28 22:03 ` David Hildenbrand
2021-01-28 22:28 ` David Rientjes
2021-01-28 22:30 ` David Hildenbrand
2021-01-29 11:34 ` [PATCH v3] " David Hildenbrand
2021-01-29 11:46 ` Oscar Salvador
2021-01-29 11:51 ` David Hildenbrand
2021-01-30 8:48 ` David Rientjes
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=20210128095906.GA5250@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=peterz@infradead.org \
--cc=richard.weiyang@linux.alibaba.com \
--cc=rppt@kernel.org \
--cc=tglx@linutronix.de \
/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).