From: Oscar Salvador <osalvador@suse.de>
To: Michal Hocko <mhocko@kernel.org>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
akpm@linux-foundation.org, dan.j.williams@intel.com,
pavel.tatashin@microsoft.com, jglisse@redhat.com,
Jonathan.Cameron@huawei.com, rafael@kernel.org, david@redhat.com,
linux-mm@kvack.org, Oscar Salvador <osalvador@suse.com>
Subject: Re: [PATCH v2 4/5] mm, memory-hotplug: Rework unregister_mem_sect_under_nodes
Date: Mon, 25 Mar 2019 09:14:48 +0100 [thread overview]
Message-ID: <20190325081445.64qmxwzpuqafhfsd@d104.suse.de> (raw)
In-Reply-To: <20190325080453.GB9924@dhcp22.suse.cz>
On Mon, Mar 25, 2019 at 09:04:53AM +0100, Michal Hocko wrote:
> No, unfortunately two nodes might share the same section indeed. Have a
> look at 4aa9fc2a435abe95a1e8d7f8c7b3d6356514b37a
Heh, I see, I guess one cannot assume anything when it comes to HW.
Well, at least we know that for real now.
I always thought that this was merely a kind of hardcoded assumption that we
just made in an attempt to avoid breaking things.
--
Oscar Salvador
SUSE L3
next prev parent reply other threads:[~2019-03-25 8:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 16:20 [PATCH v2 0/5] Do not touch pages in hot-remove path Oscar Salvador
2018-11-27 16:20 ` [PATCH v2 1/5] mm, memory_hotplug: Add nid parameter to arch_remove_memory Oscar Salvador
2018-11-27 16:20 ` [PATCH v2 2/5] kernel, resource: Check for IORESOURCE_SYSRAM in release_mem_region_adjustable Oscar Salvador
2018-11-27 16:20 ` [PATCH v2 3/5] mm, memory_hotplug: Move zone/pages handling to offline stage Oscar Salvador
2018-11-28 7:52 ` Mike Rapoport
2018-11-28 14:25 ` osalvador
2018-11-28 14:15 ` osalvador
2018-11-27 16:20 ` [PATCH v2 4/5] mm, memory-hotplug: Rework unregister_mem_sect_under_nodes Oscar Salvador
2019-03-24 6:48 ` Anshuman Khandual
2019-03-25 7:40 ` Oscar Salvador
2019-03-25 8:04 ` Michal Hocko
2019-03-25 8:14 ` Oscar Salvador [this message]
2018-11-27 16:20 ` [PATCH v2 5/5] mm, memory_hotplug: Refactor shrink_zone/pgdat_span Oscar Salvador
2018-11-28 6:50 ` Michal Hocko
2018-11-28 7:07 ` Oscar Salvador
2018-11-28 10:03 ` David Hildenbrand
2018-11-28 10:14 ` Michal Hocko
2018-11-28 11:00 ` osalvador
2018-11-28 12:31 ` Michal Hocko
2018-11-28 12:51 ` osalvador
2018-11-28 13:08 ` Michal Hocko
2018-11-28 13:18 ` osalvador
2018-11-28 15:50 ` Michal Hocko
2018-11-28 16:02 ` osalvador
2018-11-29 9:29 ` osalvador
2018-11-28 13:09 ` osalvador
2018-11-27 16:25 [PATCH v2 4/5] mm, memory-hotplug: Rework unregister_mem_sect_under_nodes 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=20190325081445.64qmxwzpuqafhfsd@d104.suse.de \
--to=osalvador@suse.de \
--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=jglisse@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=osalvador@suse.com \
--cc=pavel.tatashin@microsoft.com \
--cc=rafael@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.