[lkml]   [2018]   [Feb]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v3 1/1] mm: page_alloc: skip over regions of invalid pfns on UMA
Hello Michal,

On Mon, Jan 29, 2018 at 07:47:46PM +0100, Michal Hocko wrote:
> On Wed 24-01-18 15:35:45, Eugeniu Rosca wrote:
> [...]
> > diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> > index 76c9688b6a0a..4a3d5936a9a0 100644
> > --- a/mm/page_alloc.c
> > +++ b/mm/page_alloc.c
> > @@ -5344,14 +5344,12 @@ void __meminit memmap_init_zone(unsigned long size, int nid, unsigned long zone,
> > goto not_early;
> >
> > if (!early_pfn_valid(pfn)) {
> > /*
> > * Skip to the pfn preceding the next valid one (or
> > * end_pfn), such that we hit a valid pfn (or end_pfn)
> > * on our next iteration of the loop.
> > */
> > pfn = memblock_next_valid_pfn(pfn, end_pfn) - 1;
> > -#endif
> > continue;
> Wouldn't it be just simpler to have ifdef CONFIG_HAVE_MEMBLOCK rather
> than define memblock_next_valid_pfn for !HAVE_MEMBLOCK and then do the
> (pfn + 1 ) - 1 games.

This sounds to me like you prefer the earlier v2 of this patch.

To my understanding, the difference between v2 and v3 is mainly
meaningful for architectures which don't define CONFIG_HAVE_MEMBLOCK.
One of them is ARCH=tile (for which kbuild test robot reported a compile
failure for v1 of my patch). Out of curiosity, I compiled
mm/page_alloc.o for ARCH=tile using [PATCH v2] and [PATCH v3], then
disassembled the objects using `objdump -D` and compared the results.

What I see is that the disassembled versions of memmap_init_zone()
fully match. To me, this means that the main difference between v2 and
v3 is about code readability. This is definitely an important aspect
too, but I must admit I don't have a very strong opinion here. I expect
this to be arbitrated by MM developers and eventually by the MM

For the record, to achieve the same boot time improvement, the
alternatives on our side are:
- enable CONFIG_NUMA, just to benefit from the ~140ms speedup in boot
time. Besides the increase of kernel image size, this also leads to
annoying "Numa node 0:" noise in backtrace and stackdump output,
which is not interesting for a non-NUMA system.
- ship the patch to our customers, in spite of not being accepted by MM
community. This is a risky and unhealthy path, which we don't like.

That said, I really hope this won't be the last comment in the thread
and appropriate suggestions will come on how to go forward.

Thank you,

> I am usually against ifdefs in the code but that
> would require a larger surgery to memmap_init_zone.
> To be completely honest, I would like to see HAVE_MEMBLOCK_NODE_MAP
> gone.
> Other than that, the patch looks sane to me.
> > }
> > if (!early_pfn_in_nid(pfn, nid))
> > --
> > 2.15.1
> >
> --
> Michal Hocko
> SUSE Labs

 \ /
  Last update: 2018-02-03 13:25    [W:1.691 / U:0.204 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site