linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Shan <gshan@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	rdunlap@infradead.org, robh+dt@kernel.org, shan.gavin@gmail.com
Subject: Re: [PATCH v4] Documentation, dt, numa: Add note to empty NUMA node
Date: Fri, 25 Jun 2021 21:14:49 +1000	[thread overview]
Message-ID: <62d04903-e4f3-2302-d530-5942e33ae116@redhat.com> (raw)
In-Reply-To: <20210625101821.3t3vgj2pnw3hqpzm@gator>

On 6/25/21 8:18 PM, Andrew Jones wrote:
> On Fri, Jun 25, 2021 at 06:36:48PM +1000, Gavin Shan wrote:
>> On 6/25/21 5:06 PM, Andrew Jones wrote:
>>> On Fri, Jun 25, 2021 at 09:02:17AM +0200, Andrew Jones wrote:
>>>> On Fri, Jun 25, 2021 at 01:23:38PM +0800, Gavin Shan wrote:
>>>>> The empty memory nodes, where no memory resides in, are allowed.
>>>>> For these empty memory nodes, the 'len' of 'reg' property is zero.
>>>>> The NUMA node IDs are still valid and parsed, but memory can be
>>>>> added to them through hotplug afterwards. I finds difficulty to
>>>>> get where it's properly documented.
>>>>>
>>>>> So lets add note to empty memory nodes in the NUMA binding doc.
>>>>>
>>>>> Signed-off-by: Gavin Shan <gshan@redhat.com>
>>>>> ---
>>>>>    Documentation/devicetree/bindings/numa.txt | 4 ++++
>>>>>    1 file changed, 4 insertions(+)
>>>>>
>>>>> diff --git a/Documentation/devicetree/bindings/numa.txt b/Documentation/devicetree/bindings/numa.txt
>>>>> index 21b35053ca5a..0fc882e44270 100644
>>>>> --- a/Documentation/devicetree/bindings/numa.txt
>>>>> +++ b/Documentation/devicetree/bindings/numa.txt
>>>>> @@ -109,6 +109,10 @@ Example:
>>>>>    Dual socket system consists of 2 boards connected through ccn bus and
>>>>>    each board having one socket/soc of 8 cpus, memory and pci bus.
>>>>> +Note that empty memory nodes, which no memory resides in, are allowed.
>>>>> +The NUMA node IDs in these empty memory nodes are still valid, but
>>>>> +memory can be added into them through hotplug afterwards.
>>>>
>>>> Please change the second sentence to:
>>>>
>>>>     The NUMA node IDs in these empty memory nodes are still valid and
>>>>     memory may be added into them through hotplug afterwards.
>>>>
>>>> But, this doesn't look like the right place for this paragraph. You're
>>>> adding the paragraph to the example section, but the example doesn't have
>>>> any empty memory nodes.
>>>>
>>>> I think the paragraph should be added to section "2 - numa-node-id" and an
>>>
>>> Or maybe even create a new section for it.
>>>
>>>> example empty memory node should be provided. Also, the commit message
>>>> talks about the length of 'reg' being zero, which is an important
>>>> distinction which should also be documented.
>>>>
>>
>> Drew, thanks for your comments. Yeah, it sounds sensible to create
>> a new section for it and an example would be more helpful. Please
>> check if below changes are fine to you. I probably need Randy's review
>> again.
>>
>> I'm trying to avoid too many revisions for this sort of trivial patch,
>> even though I already had. However, it's time frame for v5.14 and I'm
>> pushing this to be merged during the cycle.
> 
> We must revise until we're satisfied... Also, I wouldn't call writing
> specifications trivial.
> 

[...]

> I'll just rewrite it:
> 
>   Empty memory nodes, which no memory resides in, are allowed. The 'length'
>   field of the 'reg' property is zero, but the 'base-address' is a dummy
>   address and invalid. However, the NUMA node IDs and distance maps are
>   still valid and memory may be added into them through hotplug afterwards.
> 

[...]

> 
> You should write how you've selected the dummy addresses for the empty
> memory nodes, perhaps here in the /* Empty memory node */ comments or
> above in the paragraph or both.
> 
>> +	memory@0x100000000 {
>> +		device_type = "memory";
>> +		reg = <0x1 0x0 0x0 0x0>;
>> +		numa-node-id = <2>;
>> +	};
>> +
>> +	/* Empty memory node */
>> +	memory@0x180000000 {
>> +		device_type = "memory";
>> +		reg = <0x1 0x80000000 0x0 0x0>;
>> +		numa-node-id = <3>;
>> +	};
>> +

[...]

Thanks, Drew. As 'base-address' is dummy address and invalid. So we
would note it as suggestion. With your suggestion integrated, how about
something like this?

==============================================================================
4 - Empty memory nodes
==============================================================================

Empty memory nodes, which no memory resides in, are allowed. The 'length'
field of the 'reg' property is zero, but the 'base-address' is a dummy
address and invalid. The 'base-address' could be the summation of highest
memory address plus the NUMA node ID. However, the NUMA node IDs and
distance maps are still valid and memory may be added into them through
hotplug afterwards.

        :

        memory@0 {
                 device_type = "memory";
                 reg = <0x0 0x0 0x0 0x80000000>;
                 numa-node-id = <0>;
         };

         memory@0x80000000 {
                 device_type = "memory";
                 reg = <0x0 0x80000000 0x0 0x80000000>;
                 numa-node-id = <1>;
         };

         /* Empty memory node */
         memory@0x100000002 {
                 device_type = "memory";
                 reg = <0x1 0x2 0x0 0x0>;
                 numa-node-id = <2>;
         };

         /* Empty memory node */
         memory@0x100000003 {
                 device_type = "memory";
                 reg = <0x1 0x3 0x0 0x0>;
                 numa-node-id = <3>;
         };

         :

Thanks,
Gavin



  reply	other threads:[~2021-06-25 11:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25  5:23 [PATCH v4] Documentation, dt, numa: Add note to empty NUMA node Gavin Shan
2021-06-25  5:29 ` Randy Dunlap
2021-06-25  7:02 ` Andrew Jones
2021-06-25  7:06   ` Andrew Jones
2021-06-25  8:36     ` Gavin Shan
2021-06-25 10:18       ` Andrew Jones
2021-06-25 11:14         ` Gavin Shan [this message]
2021-06-28  8:34           ` Andrew Jones
2021-06-28  9:38             ` Gavin Shan

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=62d04903-e4f3-2302-d530-5942e33ae116@redhat.com \
    --to=gshan@redhat.com \
    --cc=devicetree@vger.kernel.org \
    --cc=drjones@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=shan.gavin@gmail.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).