From: Oscar Salvador <osalvador@suse.de>
To: David Hildenbrand <david@redhat.com>
Cc: akpm@linux-foundation.org, mhocko@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, vbabka@suse.cz,
pasha.tatashin@soleen.com
Subject: Re: [PATCH 2/5] mm,memory_hotplug: Allocate memmap from the added memory range
Date: Mon, 25 Jan 2021 14:36:20 +0100 [thread overview]
Message-ID: <20210125133544.GA31473@linux> (raw)
In-Reply-To: <64b0dca6-4460-ec6c-66f6-88db24ec288f@redhat.com>
On Mon, Jan 25, 2021 at 12:02:53PM +0100, David Hildenbrand wrote:
> Assume you have two consecutive memory blocks with 56 sizeof(struct page).
> The first one allocates a PMD (2097152) but only consumes 1835008, the second
> one reuses the remaining part and allocates another PMD (1835008),
> only using parts of it.
>
> Ripping out a memory block, along with the PMD in the vmemmap would
> remove parts of the vmemmap of another memory block.
Bleh, yeah, I was confused, you are right.
> You might want to take a look at:
Thanks a lot for the hints, I will have a look ;-)
--
Oscar Salvador
SUSE L3
next prev parent reply other threads:[~2021-01-25 13:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 13:07 [PATCH 0/5] Allocate memmap from hotadded memory (per device) Oscar Salvador
2020-12-17 13:07 ` [PATCH 1/5] mm: Introduce ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE Oscar Salvador
2021-01-11 16:52 ` David Hildenbrand
2021-01-12 7:26 ` Oscar Salvador
2021-01-12 10:12 ` David Hildenbrand
2021-01-12 11:17 ` Oscar Salvador
2021-01-12 11:17 ` David Hildenbrand
2020-12-17 13:07 ` [PATCH 2/5] mm,memory_hotplug: Allocate memmap from the added memory range Oscar Salvador
2021-01-18 10:11 ` Oscar Salvador
2021-01-19 13:58 ` David Hildenbrand
2021-01-25 10:39 ` Oscar Salvador
2021-01-25 10:56 ` Oscar Salvador
2021-01-25 11:02 ` David Hildenbrand
2021-01-25 13:36 ` Oscar Salvador [this message]
2021-01-25 10:57 ` David Hildenbrand
2021-01-25 11:18 ` Oscar Salvador
2021-01-25 11:23 ` David Hildenbrand
2020-12-17 13:07 ` [PATCH 3/5] acpi,memhotplug: Enable MHP_MEMMAP_ON_MEMORY when supported Oscar Salvador
2021-01-11 16:53 ` David Hildenbrand
2020-12-17 13:07 ` [PATCH 4/5] powerpc/memhotplug: " Oscar Salvador
2021-01-11 16:55 ` David Hildenbrand
2021-01-12 13:31 ` Oscar Salvador
2020-12-17 13:07 ` [PATCH 5/5] mm,memory_hotplug: Add kernel boot option to enable memmap_on_memory Oscar Salvador
2021-01-11 9:05 ` [PATCH 0/5] Allocate memmap from hotadded memory (per device) 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=20210125133544.GA31473@linux \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=pasha.tatashin@soleen.com \
--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 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.