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]
Date:   Tue, 16 May 2023 11:59:07 +0000
From:   "Yajun Deng" <yajun.deng@...ux.dev>
To:     "Borislav Petkov" <bp@...en8.de>
Cc:     tony.luck@...el.com, james.morse@....com, mchehab@...nel.org,
        rric@...nel.org, corbet@....net, linux-kernel@...r.kernel.org,
        linux-edac@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH] EDAC: Expose node link in sysfs if CONFIG_NUMA

May 16, 2023 7:19 PM, "Borislav Petkov" <bp@...en8.de> wrote:

> On Tue, May 16, 2023 at 11:07:11AM +0000, Yajun Deng wrote:
> 
>> It will help users to confirm which MC belongs to which node if there
>> are multiple MCs. Therefore, we can also know how many dimm on each
>> node.
> 
> There are physical nodes, logical nodes, NUMA nodes, interleaving
> between nodes...
> 

Node is the NUMA node, We get the numa id by calling dev_to_node().

> Is there any practical use case and need behind this?
>

Some dimm may not be recognized when boot, we want to find it.

The '/sys/devices/system/node/node0/meminfo' would show the memory on
node0.

If we have '/sys/devices/system/node/node0/mc0', by comparing the number
of dimm and MemTotal in meminfo. It is easy to know that the dimm didn't 
recognized whether it belonged to this NUMA node or not.

 
> --
> Regards/Gruss,
> Boris.
> 
> https://people.kernel.org/tglx/notes-about-netiquette

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ