[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210120132223.GH4605@ziepe.ca>
Date: Wed, 20 Jan 2021 09:22:23 -0400
From: Jason Gunthorpe <jgg@...pe.ca>
To: Pavel Tatashin <pasha.tatashin@...een.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
akpm@...ux-foundation.org, vbabka@...e.cz, mhocko@...e.com,
david@...hat.com, osalvador@...e.de, dan.j.williams@...el.com,
sashal@...nel.org, tyhicks@...ux.microsoft.com,
iamjoonsoo.kim@....com, mike.kravetz@...cle.com,
rostedt@...dmis.org, mingo@...hat.com, peterz@...radead.org,
mgorman@...e.de, willy@...radead.org, rientjes@...gle.com,
jhubbard@...dia.com, linux-doc@...r.kernel.org,
ira.weiny@...el.com, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH v6 10/14] memory-hotplug.rst: add a note about
ZONE_MOVABLE and page pinning
On Tue, Jan 19, 2021 at 08:43:29PM -0500, Pavel Tatashin wrote:
> +.. note::
> + Techniques that rely on long-term pinnings of memory (especially, RDMA and
> + vfio) are fundamentally problematic with ZONE_MOVABLE and, therefore, memory
> + hot remove. Pinned pages cannot reside on ZONE_MOVABLE, to guarantee that
> + memory can still get hot removed - be aware that pinning can fail even if
> + there is plenty of free memory in ZONE_MOVABLE. In addition, using
> + ZONE_MOVABLE might make page pinning more expensive, because pages have to be
> + migrated off that zone first.
Just to point out, if anyone is using RDMA/etc with hotplug memory,
this series is likekly going to be a major regression for those users.
Jason
Powered by blists - more mailing lists