From: Andrew Morton <akpm@linux-foundation.org>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: linux-mm@kvack.org,
Mike Rapoport Baoquan He <"rppt@kernel.orgbhe"@redhat.com>,
David Hildenbrand <david@redhat.com>,
Mel Gorman <mgorman@suse.de>, Michal Hocko <mhocko@kernel.org>,
Qian Cai <cai@lca.pw>, Vlastimil Babka <vbabka@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] mm: initialize struct pages in reserved regions outside of the zone ranges
Date: Fri, 4 Dec 2020 21:10:36 -0800 [thread overview]
Message-ID: <20201204211036.48092c4bc83dabd1419f9c71@linux-foundation.org> (raw)
In-Reply-To: <20201205013238.21663-1-aarcange@redhat.com>
On Fri, 4 Dec 2020 20:32:37 -0500 Andrea Arcangeli <aarcange@redhat.com> wrote:
> I'm running with these patch applied on all instances as solution to
> the compaction crashes that started to trigger after the v5.9
> upgrade. It's applied on top of
> https://lore.kernel.org/lkml/20201201181502.2340-1-rppt@kernel.org so
> that it boots and works fine even when there are memblock.reserved
> regions that don't overlap with the memblock.memory (as pfn 0 which is
> in memblock.reserved but not added to memblock.memory).
Are you planning on preparing an applicable-to-mainline version of this?
prev parent reply other threads:[~2020-12-05 5:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 18:15 [PATCH] mm: refactor initialization of stuct page for holes in memory layout Mike Rapoport
2020-12-02 23:47 ` Andrew Morton
2020-12-03 6:25 ` Mike Rapoport
2020-12-03 18:34 ` Andrea Arcangeli
2020-12-05 1:32 ` [PATCH 0/1] mm: initialize struct pages in reserved regions outside of the zone ranges Andrea Arcangeli
2020-12-05 1:32 ` [PATCH 1/1] " Andrea Arcangeli
2020-12-05 5:10 ` Andrew Morton [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=20201204211036.48092c4bc83dabd1419f9c71@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc="rppt@kernel.orgbhe"@redhat.com \
--cc=aarcange@redhat.com \
--cc=cai@lca.pw \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).