[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dece66a05bb63a04706d25ca86f75bfc875c27fd.camel@intel.com>
Date: Wed, 08 Jun 2022 12:19:52 +0800
From: Ying Huang <ying.huang@...el.com>
To: Johannes Weiner <hannes@...xchg.org>, linux-mm@...ck.org
Cc: Hao Wang <haowang3@...com>, Abhishek Dhanotia <abhishekd@...com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Yang Shi <yang.shi@...ux.alibaba.com>,
Tim Chen <tim.c.chen@...ux.intel.com>,
Davidlohr Bueso <dave@...olabs.net>,
Adam Manzanares <a.manzanares@...sung.com>,
linux-kernel@...r.kernel.org, kernel-team@...com,
Hasan Al Maruf <hasanalmaruf@...com>,
Wei Xu <weixugc@...gle.com>,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.ibm.com>,
Yang Shi <shy828301@...il.com>
Subject: Re: [PATCH] mm: mempolicy: N:M interleave policy for tiered memory
nodes
On Tue, 2022-06-07 at 13:19 -0400, Johannes Weiner wrote:
> From: Hasan Al Maruf <hasanalmaruf@...com>
>
> Existing interleave policy spreads out pages evenly across a set of
> specified nodes, i.e. 1:1 interleave. Upcoming tiered memory systems
> have CPU-less memory nodes with different peak bandwidth and
> latency-bandwidth characteristics. In such systems, we will want to
> use the additional bandwidth provided by lowtier memory for
> bandwidth-intensive applications. However, the default 1:1 interleave
> can lead to suboptimal bandwidth distribution.
>
> Introduce an N:M interleave policy, where N pages allocated to the
> top-tier nodes are followed by M pages allocated to lowtier nodes.
> This provides the capability to steer the fraction of memory traffic
> that goes to toptier vs. lowtier nodes. For example, 4:1 interleave
> leads to an 80%/20% traffic breakdown between toptier and lowtier.
>
> The ratios are configured through a new sysctl:
>
> vm.numa_tier_interleave = toptier lowtier
>
> We have run experiments on bandwidth-intensive production services on
> CXL-based tiered memory systems, where lowtier CXL memory has, when
> compared to the toptier memory directly connected to the CPU:
>
> - ~half of the peak bandwidth
> - ~80ns higher idle latency
> - steeper latency vs. bandwidth curve
>
> Results show that regular interleaving leads to a ~40% performance
> regression over baseline; 5:1 interleaving shows an ~8% improvement
> over baseline. We have found the optimal distribution changes based on
> hardware characteristics: slower CXL memory will shift the optimal
> breakdown from 5:1 to (e.g.) 8:1.
>
> The sysctl only applies to processes and vmas with an "interleave"
> policy and has no bearing on contexts using prefer or bind policies.
>
> It defaults to a setting of "1 1", which represents even interleaving,
> and so is backward compatible with existing setups.
>
> Signed-off-by: Hasan Al Maruf <hasanalmaruf@...com>
> Signed-off-by: Hao Wang <haowang3@...com>
> Signed-off-by: Johannes Weiner <hannes@...xchg.org>
In general, I think the use case is valid. But we are changing memory
tiering now, including
- make memory tiering explict
- support more than 2 tiers
- expose memory tiering via sysfs
Details can be found int the following threads,
https://lore.kernel.org/lkml/CAAPL-u9Wv+nH1VOZTj=9p9S70Y3Qz3+63EkqncRDdHfubsrjfw@mail.gmail.com/
https://lore.kernel.org/lkml/20220603134237.131362-1-aneesh.kumar@linux.ibm.com/
With these changes, we may need to revise your implementation. For
example, put interleave knobs in memory tier sysfs interface, support
more than 2 tiers, etc.
Best Regards,
Huang, Ying
[snip]
Powered by blists - more mailing lists