From: David Hildenbrand <david@redhat.com>
To: Michal Hocko <mhocko@suse.com>,
Pavel Tatashin <pasha.tatashin@soleen.com>
Cc: Vlastimil Babka <vbabka@suse.cz>, linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Oscar Salvador <osalvador@suse.de>,
Dan Williams <dan.j.williams@intel.com>,
Sasha Levin <sashal@kernel.org>,
Tyler Hicks <tyhicks@linux.microsoft.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
sthemmin@microsoft.com, John Hubbard <jhubbard@nvidia.com>
Subject: Re: Pinning ZONE_MOVABLE pages
Date: Tue, 24 Nov 2020 09:44:33 +0100 [thread overview]
Message-ID: <43922bf4-c818-e675-2369-10097c460ac4@redhat.com> (raw)
In-Reply-To: <20201124084350.GU27488@dhcp22.suse.cz>
On 24.11.20 09:43, Michal Hocko wrote:
> On Mon 23-11-20 11:31:59, Pavel Tatashin wrote:
> [...]
>> Also, we still need to take care of the fault scenario.
>
> Forgot to reply to this part. I believe you mean this to be fault at gup
> time, right? Then the easiest way forward would be to either add yet
> another scoped flag or (maybe) better to generalize memalloc_nocma_* to
> imply that the allocated memory is going to be unmovable so drop
> __GFP_MOVABLE and also forbid CMA. I have to admit that I do not
> remember why long term pin on CMA pages is ok to go to movable but I
> strongly suspect this is just shifting problem around.
Agreed.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-11-24 8:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 20:27 Pinning ZONE_MOVABLE pages Pavel Tatashin
2020-11-20 20:59 ` David Hildenbrand
2020-11-20 21:17 ` Matthew Wilcox
2020-11-20 21:34 ` David Hildenbrand
2020-11-20 21:53 ` Pavel Tatashin
2020-11-20 21:58 ` Pavel Tatashin
2020-11-20 22:06 ` David Hildenbrand
2020-11-22 21:06 ` David Rientjes
2020-11-23 15:31 ` Pavel Tatashin
2020-11-23 9:01 ` Michal Hocko
2020-11-23 16:06 ` Pavel Tatashin
2020-11-23 17:15 ` Jason Gunthorpe
2020-11-23 17:54 ` Pavel Tatashin
2020-11-23 18:34 ` Jason Gunthorpe
2020-11-24 8:20 ` Michal Hocko
2020-11-23 15:04 ` Vlastimil Babka
2020-11-23 16:31 ` Pavel Tatashin
2020-11-24 8:24 ` Michal Hocko
2020-11-24 8:43 ` Michal Hocko
2020-11-24 8:44 ` David Hildenbrand [this message]
2020-11-24 6:49 ` John Hubbard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43922bf4-c818-e675-2369-10097c460ac4@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=sashal@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=tyhicks@linux.microsoft.com \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).