From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
Alexander Duyck <alexander.h.duyck@linux.intel.com>,
Alexander Potapenko <glider@google.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Arun KS <arunks@codeaurora.org>,
Dan Williams <dan.j.williams@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mel Gorman <mgorman@techsingularity.net>,
Michael Ellerman <mpe@ellerman.id.au>,
Michal Hocko <mhocko@suse.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Oscar Salvador <osalvador@suse.de>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Pingfan Liu <kernelfans@gmail.com>, Qian Cai <cai@lca.pw>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Vlastimil Babka <vbabka@suse.cz>,
Wei Yang <richardw.yang@linux.intel.com>
Subject: Re: [PATCH v2 0/2] mm: remove the memory isolate notifier
Date: Mon, 2 Dec 2019 11:27:14 +0100 [thread overview]
Message-ID: <990e19a3-b758-aaca-0ea2-c04e191cb6dc@redhat.com> (raw)
In-Reply-To: <20191114131911.11783-1-david@redhat.com>
On 14.11.19 14:19, David Hildenbrand wrote:
> This is the MM part of
> https://lkml.org/lkml/2019/10/31/487
>
> "We can get rid of the memory isolate notifier by switching to balloon
> compaction in powerpc's CMM (Collaborative Memory Management). The memory
> isolate notifier was only necessary to allow to offline memory blocks that
> contain inflated/"loaned" pages - which also possible when the inflated
> pages are movable (via balloon compaction). [...]"
>
> Michael queued the POWERPC bits that remove the single user, but I am
> missing ACKs for the MM bits. I think it makes sense to let these two
> patches also go via Michael's tree, to avoid collissions. Thoughts?
The prereqs (powerpc bits) are upstream - I assume Michael didn't want
to mess with MM patches. @Andrew, please pick these up once you feel
like time for them has come. :)
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-12-02 10:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 13:19 [PATCH v2 0/2] mm: remove the memory isolate notifier David Hildenbrand
2019-11-14 13:19 ` [PATCH v2 1/2] " David Hildenbrand
2019-11-14 19:39 ` Michal Hocko
2019-11-15 3:06 ` Greg Kroah-Hartman
2019-11-14 13:19 ` [PATCH v2 2/2] mm: remove "count" parameter from has_unmovable_pages() David Hildenbrand
2019-11-14 19:40 ` Michal Hocko
2019-11-15 13:00 ` [PATCH v2 0/2] mm: remove the memory isolate notifier David Hildenbrand
2019-12-02 10:27 ` David Hildenbrand [this message]
2019-12-09 11:15 ` Michael Ellerman
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=990e19a3-b758-aaca-0ea2-c04e191cb6dc@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=arunks@codeaurora.org \
--cc=cai@lca.pw \
--cc=dan.j.williams@intel.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernelfans@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mpe@ellerman.id.au \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=rafael@kernel.org \
--cc=richardw.yang@linux.intel.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--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).