From: John Hubbard <jhubbard@nvidia.com>
To: Oscar Salvador <osalvador@suse.de>, <akpm@linux-foundation.org>
Cc: <mhocko@suse.com>, <david@redhat.com>, <dan.j.williams@intel.com>,
<Jonathan.Cameron@huawei.com>, <anshuman.khandual@arm.com>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH 0/4] mm,memory_hotplug: allocate memmap from hotadded memory
Date: Fri, 29 Mar 2019 15:23:00 -0700 [thread overview]
Message-ID: <91cfdf41-ef43-1f18-36b8-806e246538a0@nvidia.com> (raw)
In-Reply-To: <20190328134320.13232-1-osalvador@suse.de>
On 3/28/19 6:43 AM, Oscar Salvador wrote:
> Hi,
>
> since last two RFCs were almost unnoticed (thanks David for the feedback),
> I decided to re-work some parts to make it more simple and give it a more
> testing, and drop the RFC, to see if it gets more attention.
> I also added David's feedback, so now all users of add_memory/__add_memory/
> add_memory_resource can specify whether they want to use this feature or not.
> I also fixed some compilation issues when CONFIG_SPARSEMEM_VMEMMAP is not set.
>
Hi Oscar, say, what tree and/or commit does this series apply to? I'm having some
trouble finding the right place. Sorry for the easy question, I did try quite
a few trees already...
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2019-03-29 22:23 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 13:43 Oscar Salvador
2019-03-28 13:43 ` [PATCH 1/4] mm, memory_hotplug: cleanup memory offline path Oscar Salvador
2019-04-03 8:43 ` Michal Hocko
2019-03-28 13:43 ` [PATCH 2/4] mm, memory_hotplug: provide a more generic restrictions for memory hotplug Oscar Salvador
2019-04-03 8:46 ` Michal Hocko
2019-04-03 8:48 ` David Hildenbrand
2019-04-04 10:04 ` Oscar Salvador
2019-04-04 10:06 ` David Hildenbrand
2019-04-04 10:31 ` Michal Hocko
2019-04-04 12:04 ` Oscar Salvador
2019-03-28 13:43 ` [PATCH 3/4] mm, memory_hotplug: allocate memmap from the added memory range for sparse-vmemmap Oscar Salvador
2019-03-28 13:43 ` [PATCH 4/4] mm, sparse: rename kmalloc_section_memmap, __kfree_section_memmap Oscar Salvador
2019-03-28 15:09 ` [PATCH 0/4] mm,memory_hotplug: allocate memmap from hotadded memory David Hildenbrand
2019-03-28 15:31 ` David Hildenbrand
2019-03-29 8:45 ` Oscar Salvador
2019-03-29 8:56 ` David Hildenbrand
2019-03-29 9:01 ` David Hildenbrand
2019-03-29 9:20 ` Oscar Salvador
2019-03-29 13:42 ` Michal Hocko
2019-04-01 7:59 ` Oscar Salvador
2019-04-01 11:53 ` Michal Hocko
2019-04-02 8:28 ` Oscar Salvador
2019-04-02 8:39 ` David Hildenbrand
2019-04-02 12:48 ` Michal Hocko
2019-04-03 8:01 ` Oscar Salvador
2019-04-03 8:12 ` Michal Hocko
2019-04-03 8:17 ` David Hildenbrand
2019-04-03 8:37 ` Michal Hocko
2019-04-03 8:41 ` David Hildenbrand
2019-04-03 8:49 ` Michal Hocko
2019-04-03 8:53 ` David Hildenbrand
2019-04-03 8:50 ` Oscar Salvador
2019-04-03 8:54 ` David Hildenbrand
2019-04-03 9:40 ` Oscar Salvador
2019-04-03 10:46 ` Michal Hocko
2019-04-04 10:25 ` Vlastimil Babka
2019-04-03 8:34 ` Oscar Salvador
2019-04-03 8:36 ` David Hildenbrand
2019-03-29 8:30 ` Oscar Salvador
2019-03-29 8:51 ` David Hildenbrand
2019-03-29 22:23 ` John Hubbard [this message]
2019-04-01 7:52 ` Oscar Salvador
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=91cfdf41-ef43-1f18-36b8-806e246538a0@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.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