Re: [PATCH] mm: allow deferred page init for vmemmap only

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: mhocko@xxxxxxxxxx
Subject: Re: [PATCH] mm: allow deferred page init for vmemmap only
From: Pavel Tatashin <pasha.tatashin@xxxxxxxxxx>
Date: Thu, 10 May 2018 11:55:42 +0000
Cc: Steven Sistare <steven.sistare@xxxxxxxxxx>, Daniel Jordan <daniel.m.jordan@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, tglx@xxxxxxxxxxxxx, Linux Memory Management List <linux-mm@xxxxxxxxx>, mgorman@xxxxxxxxxxxxxxxxxxx, mingo@xxxxxxxxxx, peterz@xxxxxxxxxxxxx, Steven Rostedt <rostedt@xxxxxxxxxxx>, Fengguang Wu <fengguang.wu@xxxxxxxxx>, Dennis Zhou <dennisszhou@xxxxxxxxx>
In-reply-to: <20180509210920.GZ32366@dhcp22.suse.cz>
References: <20180509191713.23794-1-pasha.tatashin@oracle.com> <20180509210920.GZ32366@dhcp22.suse.cz>

> This doesn't really explain why CONFIG_SPARSMEM or DISCONTIG has the
> problem.

Hi Michal,

Thank you for reviewing this patch. I sent out a version two of this patch,
with expanded explanation of the problem.

Thank you,
Pavel

References:
- [PATCH] mm: allow deferred page init for vmemmap only
  - From: Pavel Tatashin
- Re: [PATCH] mm: allow deferred page init for vmemmap only
  - From: Michal Hocko

Prev by Date: [PATCH v2] mm: allow deferred page init for vmemmap only
Next by Date: Re: [PATCH] mm/memory_hotplug: Fix leftover use of struct page during hotplug
Previous by thread: Re: [PATCH] mm: allow deferred page init for vmemmap only
Next by thread: [PATCH v2 0/8] Introduce refcount_dec_and_lock_irqsave()
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux