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: <65b77f7f89361144602dce208ba4cb32387cf330.camel@intel.com>
Date:   Wed, 08 Jun 2022 16:34:59 +0800
From:   Ying Huang <ying.huang@...el.com>
To:     Aneesh Kumar K V <aneesh.kumar@...ux.ibm.com>, linux-mm@...ck.org,
        akpm@...ux-foundation.org
Cc:     Wei Xu <weixugc@...gle.com>, Greg Thelen <gthelen@...gle.com>,
        Yang Shi <shy828301@...il.com>,
        Davidlohr Bueso <dave@...olabs.net>,
        Tim C Chen <tim.c.chen@...el.com>,
        Brice Goglin <brice.goglin@...il.com>,
        Michal Hocko <mhocko@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Hesham Almatary <hesham.almatary@...wei.com>,
        Dave Hansen <dave.hansen@...el.com>,
        Jonathan Cameron <Jonathan.Cameron@...wei.com>,
        Alistair Popple <apopple@...dia.com>,
        Dan Williams <dan.j.williams@...el.com>,
        Feng Tang <feng.tang@...el.com>,
        Jagdish Gediya <jvgediya@...ux.ibm.com>,
        Baolin Wang <baolin.wang@...ux.alibaba.com>,
        David Rientjes <rientjes@...gle.com>
Subject: Re: [PATCH v5 6/9] mm/demotion: Add support for removing node from
 demotion memory tiers

On Wed, 2022-06-08 at 13:59 +0530, Aneesh Kumar K V wrote:
> On 6/8/22 1:53 PM, Ying Huang wrote:
> > On Wed, 2022-06-08 at 13:50 +0530, Aneesh Kumar K V wrote:
> > > On 6/8/22 12:29 PM, Ying Huang wrote:
> > > > On Fri, 2022-06-03 at 19:12 +0530, Aneesh Kumar K.V wrote:
> > > > > This patch adds the special string "none" as a supported memtier value
> > > > > that we can use to remove a specific node from being using as demotion target.
> > > > > 
> > > > > For ex:
> > > > > :/sys/devices/system/node/node1# cat memtier
> > > > > 1
> > > > > :/sys/devices/system/node/node1# cat ../../memtier/memtier1/nodelist
> > > > > 1-3
> > > > > :/sys/devices/system/node/node1# echo none > memtier
> > > > > :/sys/devices/system/node/node1#
> > > > > :/sys/devices/system/node/node1# cat memtier
> > > > > :/sys/devices/system/node/node1# cat ../../memtier/memtier1/nodelist
> > > > > 2-3
> > > > > :/sys/devices/system/node/node1#
> > > > 
> > > > Do you have a practical use case for this?  What kind of memory node
> > > > needs to be removed from memory tiers demotion/promotion?
> > > > 
> > > 
> > > This came up in our internal discussion. It was mentioned that there is
> > > a need to skip some slow memory nodes from participating in demotion.
> > 
> > Again, can you provide a practical use case?  Why we shouldn't demote
> > cold pages to these slow memory nodes?  How do we use these slow memory
> > node?  These slow memory node is slower than disk?
> > 
> 
> This was discussed in the context of memory borrowed from remote machine 
> (aka OpenCAPI memory). In such case, we would have a memory only NUMA 
> node which we want to avoid using for demotion.

Thanks for your information.  But why shouldn't we use them for
demotion?  Because it's too slow?  Even slower than disks?  Or some
other reason?

Best Regards,
Huang, Ying


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ