[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190604074056.GA2853@linux>
Date: Tue, 4 Jun 2019 09:41:00 +0200
From: Oscar Salvador <osalvador@...e.de>
To: Dan Williams <dan.j.williams@...el.com>
Cc: akpm@...ux-foundation.org, David Hildenbrand <david@...hat.com>,
Jane Chu <jane.chu@...cle.com>,
Michael Ellerman <mpe@...erman.id.au>,
Pavel Tatashin <pasha.tatashin@...een.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Robin Murphy <robin.murphy@....com>,
Anshuman Khandual <anshuman.khandual@....com>,
Logan Gunthorpe <logang@...tatee.com>,
Paul Mackerras <paulus@...ba.org>,
Toshi Kani <toshi.kani@....com>,
Jeff Moyer <jmoyer@...hat.com>, Michal Hocko <mhocko@...e.com>,
Vlastimil Babka <vbabka@...e.cz>, stable@...r.kernel.org,
Jérôme Glisse <jglisse@...hat.com>,
linux-nvdimm@...ts.01.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v8 00/12] mm: Sub-section memory hotplug support
On Mon, May 06, 2019 at 04:39:26PM -0700, Dan Williams wrote:
> Changes since v7 [1]:
>
> - Make subsection helpers pfn based rather than physical-address based
> (Oscar and Pavel)
>
> - Make subsection bitmap definition scalable for different section and
> sub-section sizes across architectures. As a result:
>
> unsigned long map_active
>
> ...is converted to:
>
> DECLARE_BITMAP(subsection_map, SUBSECTIONS_PER_SECTION)
>
> ...and the helpers are renamed with a 'subsection' prefix. (Pavel)
>
> - New in this version is a touch of arch/powerpc/include/asm/sparsemem.h
> in "[PATCH v8 01/12] mm/sparsemem: Introduce struct mem_section_usage"
> to define ARCH_SUBSECTION_SHIFT.
>
> - Drop "mm/sparsemem: Introduce common definitions for the size and mask
> of a section" in favor of Robin's "mm/memremap: Rename and consolidate
> SECTION_SIZE" (Pavel)
>
> - Collect some more Reviewed-by tags. Patches that still lack review
> tags: 1, 3, 9 - 12
Hi Dan,
are you planning to send V10 anytime soon?
After you addressed comments from Patch#9, the general implementation looks
fine to me and nothing sticked out from the other patches.
But I would rather wait to see v10 with the comments addressed before stamping
my Reviewed-by.
I am planning to fire my vmemmap patchset again [1], and I would like to re-base
it on top of this work, otherwise we will face many unnecessary collisions.
Thanks
[1] https://patchwork.kernel.org/patch/10875025/
--
Oscar Salvador
SUSE L3
Powered by blists - more mailing lists