Messages in this thread | | | Date | Thu, 8 Apr 2021 10:03:15 +0200 | From | Oscar Salvador <> | Subject | Re: [PATCH 01/10] mm/numa: node demotion data structure and lookup |
| |
On Thu, Apr 01, 2021 at 11:32:18AM -0700, Dave Hansen wrote: > > From: Dave Hansen <dave.hansen@linux.intel.com> > > Prepare for the kernel to auto-migrate pages to other memory nodes > with a user defined node migration table. This allows creating single > migration target for each NUMA node to enable the kernel to do NUMA > page migrations instead of simply reclaiming colder pages. A node > with no target is a "terminal node", so reclaim acts normally there. > The migration target does not fundamentally _need_ to be a single node, > but this implementation starts there to limit complexity. > > If you consider the migration path as a graph, cycles (loops) in the > graph are disallowed. This avoids wasting resources by constantly > migrating (A->B, B->A, A->B ...). The expectation is that cycles will > never be allowed. > > Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com> > Reviewed-by: Yang Shi <shy828301@gmail.com> > Cc: Wei Xu <weixugc@google.com> > Cc: David Rientjes <rientjes@google.com> > Cc: Huang Ying <ying.huang@intel.com> > Cc: Dan Williams <dan.j.williams@intel.com> > Cc: David Hildenbrand <david@redhat.com> > Cc: osalvador <osalvador@suse.de>
I think this patch and patch#2 could be squashed
Reviewed-by: Oscar Salvador <osalvador@suse.de>
-- Oscar Salvador SUSE L3
| |