linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Oscar Salvador <osalvador@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>,
	Michal Hocko <mhocko@kernel.org>,
	VlastimilBabkavbabka@suse.cz, pasha.tatashin@soleen.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Anshuman Khandual <anshuman.khandual@arm.com>
Subject: Re: [PATCH v2 0/7] Allocate memmap from hotadded memory (per device)
Date: Mon, 22 Feb 2021 12:15:10 +0100	[thread overview]
Message-ID: <20210222111506.GA23651@linux> (raw)
In-Reply-To: <20210217101851.GA28996@linux>

On Wed, Feb 17, 2021 at 11:18:59AM +0100, Oscar Salvador wrote:
> On Tue, Feb 09, 2021 at 02:38:47PM +0100, Oscar Salvador wrote:
> > Hi,
> > 
> > here is v2.
> > 
> > Changes from v1 -> v2
> >  - Addressed feedback from David
> >  - Fence off the feature in case struct page size is not
> >    multiple of PMD size or pageblock alignment cannot be guaranted
> >  - Tested on x86_64 small and large memory_blocks
> >  - Tested on arm64 4KB and 64KB page sizes (for some reason I cannot boot
> >    my VM with 16KB page size).
> > 
> >  Arm64 with 4KB page size behaves like x86_64 after [1], which made section
> >  size smaller.
> >  With 64KB, the feature gets fenced off due to pageblock alignment.
> > 
> > Changes from RFCv3 -> v1:
> >  - Addressed feedback from David
> >  - Re-order patches
> > 
> > Changes from v2 -> v3 (RFC):
> >  - Re-order patches (Michal)
> >  - Fold "mm,memory_hotplug: Introduce MHP_MEMMAP_ON_MEMORY" in patch#1
> >  - Add kernel boot option to enable this feature (Michal)
> > 
> > Changes from v1 -> v2 (RFC):
> >  - Addressed feedback provided by David
> >  - Add a arch_support_memmap_on_memory to be called
> >    from mhp_supports_memmap_on_memory, as atm,
> >    only ARM, powerpc and x86_64 have altmat support.
> > 
> > [1] https://lore.kernel.org/lkml/cover.1611206601.git.sudaraja@codeaurora.org/
> 
> Let me refloat this one :-)

Kindly ping :-)

 

-- 
Oscar Salvador
SUSE L3


  reply	other threads:[~2021-02-22 11:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 13:38 [PATCH v2 0/7] Allocate memmap from hotadded memory (per device) Oscar Salvador
2021-02-09 13:38 ` [PATCH v2 1/7] mm,memory_hotplug: Allocate memmap from the added memory range Oscar Salvador
2021-02-25 18:58   ` David Hildenbrand
2021-02-28 18:50     ` Oscar Salvador
2021-03-01  8:30       ` David Hildenbrand
2021-03-01  8:32       ` David Hildenbrand
2021-02-09 13:38 ` [PATCH v2 2/7] acpi,memhotplug: Enable MHP_MEMMAP_ON_MEMORY when supported Oscar Salvador
2021-02-09 13:38 ` [PATCH v2 3/7] mm,memory_hotplug: Add kernel boot option to enable memmap_on_memory Oscar Salvador
2021-02-25 18:25   ` David Hildenbrand
2021-02-26 12:14     ` Oscar Salvador
2021-03-01  8:27       ` David Hildenbrand
2021-02-09 13:38 ` [PATCH v2 4/7] mm,memory_hotplug: Enforce struct page size to be multiple of PMD Oscar Salvador
2021-02-25 18:26   ` David Hildenbrand
2021-02-26 12:06     ` Oscar Salvador
2021-03-01 10:06     ` Oscar Salvador
2021-03-01 10:24       ` David Hildenbrand
2021-02-09 13:38 ` [PATCH v2 5/7] mm,memory_hotplug: Enforce pageblock alignment when memmap_on_memory Oscar Salvador
2021-02-25 18:27   ` David Hildenbrand
2021-02-26 12:06     ` Oscar Salvador
2021-02-09 13:38 ` [PATCH v2 6/7] x86/Kconfig: Introduce ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE Oscar Salvador
2021-02-25 18:29   ` David Hildenbrand
2021-02-26 12:04     ` Oscar Salvador
2021-03-01  8:45       ` David Hildenbrand
2021-03-01 10:07         ` Oscar Salvador
2021-02-09 13:38 ` [PATCH v2 7/7] arm64/Kconfig: " Oscar Salvador
2021-02-25 18:29   ` David Hildenbrand
2021-02-26 12:10     ` Oscar Salvador
2021-02-17 10:18 ` [PATCH v2 0/7] Allocate memmap from hotadded memory (per device) Oscar Salvador
2021-02-22 11:15   ` Oscar Salvador [this message]
2021-02-22 11:28     ` David Hildenbrand
2021-02-23  7:48       ` 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=20210222111506.GA23651@linux \
    --to=osalvador@suse.de \
    --cc=VlastimilBabkavbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=pasha.tatashin@soleen.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).