linux-kernel - [PATCH 0/2] nodemask: Use nr_node

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-next>] [day] [month] [year] [list]

Message-ID: <20230802112458.230221601@infradead.org>
Date:   Wed, 02 Aug 2023 13:24:58 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     yury.norov@...il.com, andriy.shevchenko@...ux.intel.com,
        linux@...musvillemoes.dk
Cc:     peterz@...radead.org, Andrew Morton <akpm@...ux-foundation.org>,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org,
        tglx@...utronix.de, rppt@...nel.org
Subject: [PATCH 0/2] nodemask: Use nr_node_ids

Hi,

While working on some NUMA code recently, I stumbled over how nodemask
operations are unconditionally using MAX_NUMNODES length, which is typically
1024 for distro configs.

OTOH typical machines only have <=4 nodes, so doing these crazy long bitmap ops
is silly.

Therefore do as cpumask does and use nr_node_ids analogous to nr_cpu_ids.

These patches are lightly tested -- as in they seem to boot on a 2 node system.