From: Srikar Dronamraju <srikar@linux.ibm.com>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: sshegde@linux.ibm.com, gjoyce@linux.ibm.com, npiggin@gmail.com,
naveen.n.rao@linux.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 1/1] powerpc/numa: Online a node if PHB is attached.
Date: Mon, 20 May 2024 22:46:50 +0530 [thread overview]
Message-ID: <20240520171650.GK2531@linux.ibm.com> (raw)
In-Reply-To: <20240517142531.3273464-3-nilay@linux.ibm.com>
* Nilay Shroff <nilay@linux.ibm.com> [2024-05-17 19:55:23]:
Hi Nilay,
> In the current design, a numa-node is made online only if
> that node is attached to cpu/memory. With this design, if
> any PCI/IO device is found to be attached to a numa-node
> which is not online then the numa-node id of the corresponding
> PCI/IO device is set to NUMA_NO_NODE(-1). This design may
> negatively impact the performance of PCIe device if the
> numa-node assigned to PCIe device is -1 because in such case
> we may not be able to accurately calculate the distance
> between two nodes.
> The multi-controller NVMe PCIe disk has an issue with
> calculating the node distance if the PCIe NVMe controller
> is attached to a PCI host bridge which has numa-node id
> value set to NUMA_NO_NODE. This patch helps fix this ensuring
> that a cpu/memory less numa node is made online if it's
> attached to PCI host bridge.
>
Looks good to me.
Reviewed-by: Srikar Dronamraju <srikar@linux.ibm.com>
--
Thanks and Regards
Srikar Dronamraju
next prev parent reply other threads:[~2024-05-22 2:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 14:25 [PATCH v2 0/1] powerpc/numa: Make cpu/memory less numa-node online Nilay Shroff
2024-05-17 14:25 ` [PATCH v2 1/1] powerpc/numa: Online a node if PHB is attached Nilay Shroff
2024-05-20 17:16 ` Srikar Dronamraju [this message]
2024-05-24 13:31 ` Krishna Kumar
2024-06-20 12:49 ` [PATCH v2 0/1] powerpc/numa: Make cpu/memory less numa-node online Michael Ellerman
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=20240520171650.GK2531@linux.ibm.com \
--to=srikar@linux.ibm.com \
--cc=gjoyce@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=nilay@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=sshegde@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).