lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 10 Jan 2019 17:42:48 +0100 From: Michal Hocko <mhocko@...nel.org> To: Jerome Glisse <jglisse@...hat.com> Cc: Jonathan Cameron <jonathan.cameron@...wei.com>, Fengguang Wu <fengguang.wu@...el.com>, Andrew Morton <akpm@...ux-foundation.org>, Linux Memory Management List <linux-mm@...ck.org>, kvm@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, Fan Du <fan.du@...el.com>, Yao Yuan <yuan.yao@...el.com>, Peng Dong <dongx.peng@...el.com>, Huang Ying <ying.huang@...el.com>, Liu Jingqi <jingqi.liu@...el.com>, Dong Eddie <eddie.dong@...el.com>, Dave Hansen <dave.hansen@...el.com>, Zhang Yi <yi.z.zhang@...ux.intel.com>, Dan Williams <dan.j.williams@...el.com>, Mel Gorman <mgorman@...e.de>, Andrea Arcangeli <aarcange@...hat.com>, linux-accelerators@...ts.ozlabs.org Subject: Re: [RFC][PATCH v2 00/21] PMEM NUMA node and hotness accounting/migration On Thu 10-01-19 10:53:17, Jerome Glisse wrote: > On Tue, Jan 08, 2019 at 03:52:56PM +0100, Michal Hocko wrote: > > On Wed 02-01-19 12:21:10, Jonathan Cameron wrote: > > [...] > > > So ideally I'd love this set to head in a direction that helps me tick off > > > at least some of the above usecases and hopefully have some visibility on > > > how to address the others moving forwards, > > > > Is it sufficient to have such a memory marked as movable (aka only have > > ZONE_MOVABLE)? That should rule out most of the kernel allocations and > > it fits the "balance by migration" concept. > > This would not work for GPU, GPU driver really want to be in total > control of their memory yet sometimes they want to migrate some part > of the process to their memory. But that also means that GPU doesn't really fit the model discussed here, right? I thought HMM is the way to manage such a memory. -- Michal Hocko SUSE Labs
Powered by blists - more mailing lists