[lkml]   [2022]   [Jun]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v5 9/9] mm/demotion: Update node_is_toptier to work with memory tiers
On 6/6/22 8:41 AM, Ying Huang wrote:
> On Fri, 2022-06-03 at 19:12 +0530, Aneesh Kumar K.V wrote:
>> With memory tiers support we can have memory on NUMA nodes
>> in the top tier from which we want to avoid promotion tracking NUMA
>> faults. Update node_is_toptier to work with memory tiers. To
>> avoid taking locks, a nodemask is maintained for all demotion
>> targets. All NUMA nodes are by default top tier nodes and as
>> we add new lower memory tiers NUMA nodes get added to the
>> demotion targets thereby moving them out of the top tier.
> Check the usage of node_is_toptier(),
> - migrate_misplaced_page()
> node_is_toptier() is used to check whether migration is a promotion.
> We can avoid to use it. Just compare the rank of the nodes.
> - change_pte_range() and change_huge_pmd()
> node_is_toptier() is used to avoid scanning fast memory (DRAM) pages
> for promotion. So I think we should change the name to node_is_fast()
> as follows,
> static inline bool node_is_fast(int node)
> {
> return NODE_DATA(node)->mt_rank >= MEMORY_RANK_DRAM;
> }

But that gives special meaning to MEMORY_RANK_DRAM. As detailed in other
patches, absolute value of rank doesn't carry any meaning. It is only
the relative value w.r.t other memory tiers that decide whether it is
fast or not. Agreed by default memory tiers get built with
MEMORY_RANK_DRAM. But userspace can change the rank value of 'memtier1'
Hence to determine a node is consisting of fast memory is essentially
figuring out whether node is the top most tier in memory hierarchy and
not just the memory tier rank value is >= MEMORY_RANK_DRAM?


 \ /
  Last update: 2022-06-06 05:59    [W:0.057 / U:8.304 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site