[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b46f358b-8fea-b380-1978-5f3e772130d4@microsoft.com>
Date: Thu, 30 Aug 2018 19:38:43 +0000
From: Pasha Tatashin <Pavel.Tatashin@...rosoft.com>
To: David Hildenbrand <david@...hat.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
Jonathan Corbet <corbet@....net>,
Michal Hocko <mhocko@...e.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH RFCv2 6/6] memory-hotplug.txt: Add some details about
locking internals
Reviewed-by: Pavel Tatashin <pavel.tatashin@...rosoft.com>
On 8/21/18 6:44 AM, David Hildenbrand wrote:
> Let's document the magic a bit, especially why device_hotplug_lock is
> required when adding/removing memory and how it all play together with
> requests to online/offline memory from user space.
>
Powered by blists - more mailing lists