From: Dan Williams <dan.j.williams@intel.com>
To: Dave Jiang <dave.jiang@intel.com>, <nifan.cxl@gmail.com>,
<alison.schofield@intel.com>, <vishal.l.verma@intel.com>,
<ira.weiny@intel.com>, <dan.j.williams@intel.com>,
<Jonathan.Cameron@huawei.com>
Cc: <linux-cxl@vger.kernel.org>, <a.manzanares@samsung.com>,
<dave@stgolabs.net>, <linux-kernel@vger.kernel.org>,
<anisa.su887@gmail.com>, Fan Ni <fan.ni@samsung.com>
Subject: Re: [RFC] cxl/region: set numa node for target memdevs when a region is committed
Date: Tue, 18 Mar 2025 14:25:40 -0700 [thread overview]
Message-ID: <67d9e4d43360e_201f0294d6@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <ac564c1e-95e4-46d0-95c7-7f72c8fee0c2@intel.com>
Dave Jiang wrote:
>
>
> On 3/14/25 9:40 AM, nifan.cxl@gmail.com wrote:
> > From: Fan Ni <fan.ni@samsung.com>
> >
> > There is a sysfs attribute named "numa_node" for cxl memory device.
> > however, it is never set so -1 is returned whenever it is read.
> >
> > With this change, the numa_node of each target memdev is set based on the
> > start address of the hpa_range of the endpoint decoder it associated when a
> > cxl region is created; and it is reset when the region decoders are
> > reset.
> >
> > Open qeustion: do we need to set the numa_node when the memdev is
> > probed instead of waiting until a region is created?
>
> Typically, the numa node for a PCI device should be dev_to_node(),
> where the device resides. So when the device is probed, it should be
> set with that. See documentation [1]. Region should have its own NUMA
> node based on phys_to_target_node() of the starting address.
Right, the memdev node is the affinity of device-MMIO to a CPU. The
HDM-memory that the device decodes may land in multiple proximity
domains and is subject to CDAT, CXL QoS, HMAT Generic Port, etc...
If your memdev node is "NUMA_NO_NODE" then that likely means the
affinity information for the PCI device is missing.
I would double check that first. See set_dev_node() in device_add().
next prev parent reply other threads:[~2025-03-18 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 16:40 [RFC] cxl/region: set numa node for target memdevs when a region is committed nifan.cxl
2025-03-18 21:00 ` Dave Jiang
2025-03-18 21:25 ` Dan Williams [this message]
2025-03-18 23:11 ` Fan Ni
2025-03-19 0:16 ` Dan Williams
2025-03-21 12:22 ` Jonathan Cameron
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=67d9e4d43360e_201f0294d6@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=anisa.su887@gmail.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nifan.cxl@gmail.com \
--cc=vishal.l.verma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox