linux-kernel - Re: [PATCH] mm: migrate: set demotion targets differently

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: <55161160-1084-c81d-d116-00f5bcaa1268@intel.com>
Date:   Tue, 29 Mar 2022 07:31:12 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     Jagdish Gediya <jvgediya@...ux.ibm.com>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Cc:     akpm@...ux-foundation.org, aneesh.kumar@...ux.ibm.com,
        baolin.wang@...ux.alibaba.com, dave.hansen@...ux.intel.com,
        ying.huang@...el.com
Subject: Re: [PATCH] mm: migrate: set demotion targets differently

On 3/29/22 04:52, Jagdish Gediya wrote:
> The current implementation to identify the demotion
> targets limits some of the opportunities to share
> the demotion targets between multiple source nodes.

This changelog is a bit unsatisfying.  It basically says: the current
code isn't working, throw some more code at the problem.

I'd love to see some more information about *why* the current code
doesn't work.  Is it purely a bug or was it mis-designed?

I actually wrote it intending for it to handle cases like you describe
while not leaving lots of nodes without demotion targets.