From: hanjun.guo@linaro•org (Hanjun Guo)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC PATCH] dt:numa: adding numa node mapping for memory nodes.
Date: Tue, 28 Oct 2014 15:27:12 +0800 [thread overview]
Message-ID: <544F4550.701@linaro.org> (raw)
In-Reply-To: <20140917193452.GD7983@leverpostej>
On 2014-9-18 3:34, Mark Rutland wrote:
> On Wed, Sep 17, 2014 at 04:37:30PM +0100, Kumar Gala wrote:
>>
>> On Sep 17, 2014, at 1:56 AM, Ganapatrao Kulkarni <ganapatrao.kulkarni@caviumnetworks•com> wrote:
>>
>>> From: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium•com>
>>>
>>> This patch adds property "nid" to memory node to provide the memory range to
>>> numa node id mapping.
>>>
>>> Signed-off-by: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium•com>
>>>
>>> ?
>>
>> Adding the PPC guys as they?ve been doing NUMA on IBM Power Servers
>> for years with OF/DT. So we should really try and follow what they?ve
>> done.
>
> Agreed.
>
>>> Documentation/devicetree/bindings/numa.txt | 58 ++++++++++++++++++++++++++++++
>>> 1 file changed, 58 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/numa.txt
>>>
>>> diff --git a/Documentation/devicetree/bindings/numa.txt b/Documentation/devicetree/bindings/numa.txt
>>> new file mode 100644
>>> index 0000000..c4a94f2
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/numa.txt
>>> @@ -0,0 +1,58 @@
>>> +======================================================
>>> +numa id binding description
>>> +======================================================
>>> +
>>> +======================================================
>>> +1 - Introduction
>>> +======================================================
>>> +The device node property "nid(numa node id)" can be added to memory
>
> Why the quotes?
>
>>> +device node to map the range of memory addresses as defined in property "reg".
>>> +The property "nid" maps the memory range to the numa node id, which is used to
>>> +find the local and remory pages on numa aware systems.
>
> What is a "numa node id", exactly, and how is the OS intended to use it?
I think "Proximity Domain" would be more suitably, processors and memory or IOs
in the same domain will have better performance than crossing other domains.
Thanks
Hanjun
next prev parent reply other threads:[~2014-10-28 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 8:56 [RFC PATCH] dt:numa: adding numa node mapping for memory nodes Ganapatrao Kulkarni
2014-09-17 15:37 ` Kumar Gala
2014-09-17 19:34 ` Mark Rutland
2014-10-28 7:27 ` Hanjun Guo [this message]
2014-09-17 21:48 ` Nathan Lynch
2014-09-17 23:12 ` Zi Shen Lim
2014-09-18 4:02 ` Ganapatrao Kulkarni
2014-09-18 14:30 ` Ganapatrao Kulkarni
2014-10-28 7:50 ` Hanjun Guo
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=544F4550.701@linaro.org \
--to=hanjun.guo@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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