From: Dave Hansen <dave.hansen@intel.com>
To: Oscar Salvador <osalvador@suse.com>, linux-mm@kvack.org
Cc: mhocko@suse.com, david@redhat.com, rppt@linux.vnet.ibm.com,
akpm@linux-foundation.org, arunks@codeaurora.org, bhe@redhat.com,
dan.j.williams@intel.com, Pavel.Tatashin@microsoft.com,
Jonathan.Cameron@huawei.com, jglisse@redhat.com,
linux-kernel@vger.kernel.org, Oscar Salvador <osalvador@suse.de>
Subject: Re: [RFC PATCH 2/4] mm, memory_hotplug: provide a more generic restrictions for memory hotplug
Date: Fri, 16 Nov 2018 13:39:26 -0800 [thread overview]
Message-ID: <4063e22f-bc33-076d-5300-7bd6e61e3170@intel.com> (raw)
In-Reply-To: <20181116101222.16581-3-osalvador@suse.com>
On 11/16/18 2:12 AM, Oscar Salvador wrote:
> +/*
> + * Do we want sysfs memblock files created. This will allow userspace to online
> + * and offline memory explicitly. Lack of this bit means that the caller has to
> + * call move_pfn_range_to_zone to finish the initialization.
> + */
> +
> +#define MHP_MEMBLOCK_API 1<<0
> +
> +/* Restrictions for the memory hotplug */
> +struct mhp_restrictions {
> + unsigned long flags; /* MHP_ flags */
> + struct vmem_altmap *altmap; /* use this alternative allocatro for memmaps */
"allocatro" -> "allocator"
next prev parent reply other threads:[~2018-11-16 21:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 10:12 [RFC PATCH 0/4] mm, memory_hotplug: allocate memmap from hotadded memory Oscar Salvador
2018-11-16 10:12 ` [RFC PATCH 1/4] mm, memory_hotplug: cleanup memory offline path Oscar Salvador
2018-11-16 10:12 ` [RFC PATCH 2/4] mm, memory_hotplug: provide a more generic restrictions for memory hotplug Oscar Salvador
2018-11-16 21:39 ` Dave Hansen [this message]
2018-11-23 13:00 ` Michal Hocko
2019-01-14 13:17 ` Oscar Salvador
2018-11-16 10:12 ` [RFC PATCH 3/4] mm, memory_hotplug: allocate memmap from the added memory range for sparse-vmemmap Oscar Salvador
2018-11-16 22:41 ` Dave Hansen
2018-11-18 22:54 ` osalvador
2018-11-16 10:12 ` [RFC PATCH 4/4] mm, sparse: rename kmalloc_section_memmap, __kfree_section_memmap Oscar Salvador
2018-11-22 9:21 ` [RFC PATCH 0/4] mm, memory_hotplug: allocate memmap from hotadded memory David Hildenbrand
2018-11-23 11:55 ` Oscar Salvador
2018-11-23 12:11 ` David Hildenbrand
2018-11-23 12:42 ` Michal Hocko
2018-11-23 12:51 ` David Hildenbrand
2018-11-23 13:12 ` Michal Hocko
2018-11-26 13:05 ` David Hildenbrand
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=4063e22f-bc33-076d-5300-7bd6e61e3170@intel.com \
--to=dave.hansen@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Pavel.Tatashin@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=arunks@codeaurora.org \
--cc=bhe@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.com \
--cc=osalvador@suse.de \
--cc=rppt@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).