From: "Yajun Deng" <yajun.deng@linux.dev>
To: "Borislav Petkov" <bp@alien8.de>
Cc: tony.luck@intel.com, james.morse@arm.com, mchehab@kernel.org,
rric@kernel.org, corbet@lwn.net, linux-kernel@vger.kernel.org,
linux-edac@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] EDAC: Expose node link in sysfs if CONFIG_NUMA
Date: Tue, 16 May 2023 11:59:07 +0000 [thread overview]
Message-ID: <3509bcc597e37616cf45247e8f92d369@linux.dev> (raw)
In-Reply-To: <20230516111942.GCZGNmzu3Abd4KmZu3@fat_crate.local>
May 16, 2023 7:19 PM, "Borislav Petkov" <bp@alien8.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
next prev parent reply other threads:[~2023-05-16 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 8:07 [PATCH] EDAC: Expose node link in sysfs if CONFIG_NUMA Yajun Deng
2023-05-16 10:34 ` Borislav Petkov
2023-05-16 11:07 ` Yajun Deng
2023-05-16 11:19 ` Borislav Petkov
2023-05-16 11:59 ` Yajun Deng [this message]
2023-05-16 12:10 ` Borislav Petkov
2023-05-16 17:25 ` Luck, Tony
2023-05-17 2:49 ` Yajun Deng
2023-05-17 7:43 ` Bagas Sanjaya
2023-05-22 7:04 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3509bcc597e37616cf45247e8f92d369@linux.dev \
--to=yajun.deng@linux.dev \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=james.morse@arm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rric@kernel.org \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.