Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1655262
| From | Reza Arbab <arbab@linux.vnet.ibm.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes |
| Date | 2017-06-01 17:50 +0200 |
| Message-ID | <tNAwi-4oP-35@gated-at.bofh.it> (permalink) |
| References | <tNxoK-2tN-3@gated-at.bofh.it> <tNz7c-3D6-35@gated-at.bofh.it> <tNzgS-3Gr-17@gated-at.bofh.it> <tNA3g-4do-21@gated-at.bofh.it> <tNAmB-4kR-9@gated-at.bofh.it> |
| Organization | IBM Linux Technology Center |
On Thu, Jun 01, 2017 at 05:38:38PM +0200, Michal Hocko wrote: >On Thu 01-06-17 10:19:36, Reza Arbab wrote: >> The x86 SRAT (or the dt, on other platforms) can describe memory as >> hotpluggable. See memblock_mark_hotplug(). That's only for memory present at >> boot, though. > >Yes but lose that information after the memblock is gone and numa fully >initialized. Or can we reconstruct that somehow? I'm not sure you'd have to. At boot time, those markings are used to determine the initial boundaries of ZONE_MOVABLE. So if you removed these memblocks, then readded them, they would still be in ZONE_MOVABLE. >> He's saying that since the memory was added after boot, it is by >> definition hotpluggable. There's no need to check for that >> marking/description. > >Yes, but we do not know whether we are onlining memblocks from a boot >time numa node or a fresh one which has been hotadded. That's true. -- Reza Arbab
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes Michal Hocko <mhocko@kernel.org> - 2017-06-01 14:30 +0200
Re: [RFC PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes Vlastimil Babka <vbabka@suse.cz> - 2017-06-01 16:20 +0200
Re: [RFC PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes Michal Hocko <mhocko@kernel.org> - 2017-06-01 16:30 +0200
Re: [RFC PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes Reza Arbab <arbab@linux.vnet.ibm.com> - 2017-06-01 17:20 +0200
Re: [RFC PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes Michal Hocko <mhocko@kernel.org> - 2017-06-01 17:40 +0200
Re: [RFC PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes Reza Arbab <arbab@linux.vnet.ibm.com> - 2017-06-01 17:50 +0200
Re: [RFC PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes Michal Hocko <mhocko@kernel.org> - 2017-06-01 18:00 +0200
Re: [RFC PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes Reza Arbab <arbab@linux.vnet.ibm.com> - 2017-06-01 18:10 +0200
Re: [RFC PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes Reza Arbab <arbab@linux.vnet.ibm.com> - 2017-06-01 18:10 +0200
Re: [RFC PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes Michal Hocko <mhocko@kernel.org> - 2017-06-01 18:20 +0200
Re: [RFC PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes Reza Arbab <arbab@linux.vnet.ibm.com> - 2017-06-01 18:50 +0200
Re: [RFC PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes Michal Hocko <mhocko@kernel.org> - 2017-06-05 10:20 +0200
csiph-web