linux-kernel - Re: [PATCH] mm: mempolicy: N:M interleave policy for tiered memory nodes

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YqCvLM/ZMupRPpXP@cmpxchg.org>
Date:   Wed, 8 Jun 2022 10:16:12 -0400
From:   Johannes Weiner <hannes@...xchg.org>
To:     Ying Huang <ying.huang@...el.com>
Cc:     linux-mm@...ck.org, 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 Wed, Jun 08, 2022 at 12:19:52PM +0800, Ying Huang wrote:
> In general, I think the use case is valid.

Excellent!

> 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.

Yeah, I was expecting the interface to be the main sticking point ;)
I'll rebase this patch as the mentioned discussions find consensus.

Thanks!