From: Dave Hansen <dave.hansen@intel.com>
To: Yang Shi <shy828301@gmail.com>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Yang Shi <yang.shi@linux.alibaba.com>,
David Rientjes <rientjes@google.com>,
Huang Ying <ying.huang@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH 00/10] [v6] Migrate Pages in lieu of discard
Date: Tue, 9 Mar 2021 13:52:42 -0800 [thread overview]
Message-ID: <da1e995f-0b96-7bd5-ea49-281aabe7f46f@intel.com> (raw)
In-Reply-To: <CAHbLzkofXg0CnCBYdtWf3cE8Do=B35ZsupV01EmR1SX5=7BHjw@mail.gmail.com>
...
>> == Open Issues ==
>>
>> * For cpusets and memory policies that restrict allocations
>> to PMEM, is it OK to demote to PMEM? Do we need a cgroup-
>> level API to opt-in or opt-out of these migrations?
>
> I'm wondering if such usecases, which don't want to have memory
> allocate on pmem, will allow memory swapped out or reclaimed? If swap
> is allowed then I failed to see why migrating to pmem should be
> disallowed. If swap is not allowed, they should call mlock, then the
> memory won't be migrated to pmem as well.
Agreed. I have a hard time imagining there are a lot of folks that can
tolerate the massive overhead from swapping, but can't tolerate the much
smaller overhead of going to pmem instead of DRAM.
prev parent reply other threads:[~2021-03-09 21:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 23:59 [PATCH 00/10] [v6] Migrate Pages in lieu of discard Dave Hansen
2021-03-04 23:59 ` [PATCH 01/10] mm/numa: node demotion data structure and lookup Dave Hansen
2021-03-08 23:58 ` Yang Shi
2021-03-04 23:59 ` [PATCH 02/10] mm/numa: automatically generate node migration order Dave Hansen
2021-03-08 23:59 ` Yang Shi
2021-03-04 23:59 ` [PATCH 03/10] mm/migrate: update node demotion order during on hotplug events Dave Hansen
2021-03-09 0:03 ` Yang Shi
2021-03-09 22:07 ` Dave Hansen
2021-03-04 23:59 ` [PATCH 04/10] mm/migrate: make migrate_pages() return nr_succeeded Dave Hansen
2021-03-09 0:05 ` Yang Shi
2021-03-04 23:59 ` [PATCH 05/10] mm/migrate: demote pages during reclaim Dave Hansen
2021-03-09 0:10 ` Yang Shi
2021-03-09 23:05 ` Dave Hansen
2021-03-05 0:00 ` [PATCH 06/10] mm/vmscan: add page demotion counter Dave Hansen
2021-03-09 0:11 ` Yang Shi
2021-03-05 0:00 ` [PATCH 07/10] mm/vmscan: add helper for querying ability to age anonymous pages Dave Hansen
2021-03-09 0:14 ` Yang Shi
2021-03-20 4:05 ` Greg Thelen
2021-03-05 0:00 ` [PATCH 08/10] mm/vmscan: Consider anonymous pages without swap Dave Hansen
2021-03-09 0:17 ` Yang Shi
2021-03-09 23:08 ` Dave Hansen
2021-03-05 0:00 ` [PATCH 09/10] mm/vmscan: never demote for memcg reclaim Dave Hansen
2021-03-09 0:17 ` Yang Shi
2021-03-05 0:00 ` [PATCH 10/10] mm/migrate: new zone_reclaim_mode to enable reclaim migration Dave Hansen
2021-03-09 0:24 ` Yang Shi
2021-03-09 21:53 ` Dave Hansen
2021-03-09 0:34 ` [PATCH 00/10] [v6] Migrate Pages in lieu of discard Yang Shi
2021-03-09 21:52 ` Dave Hansen [this message]
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=da1e995f-0b96-7bd5-ea49-281aabe7f46f@intel.com \
--to=dave.hansen@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=rientjes@google.com \
--cc=shy828301@gmail.com \
--cc=yang.shi@linux.alibaba.com \
--cc=ying.huang@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.