linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: Balbir Singh <bsingharora@gmail.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
	Reza Arbab <arbab@linux.vnet.ibm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Bharata B Rao <bharata@linux.vnet.ibm.com>,
	Shailendra Singh <shailendras@nvidia.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
	<linuxppc-dev@lists.ozlabs.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Michael Bringmann from Kernel Team <mbringm@us.ibm.com>
Subject: Re: RESEND Re: [Patch 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc
Date: Wed, 14 Jun 2017 08:41:03 -0500	[thread overview]
Message-ID: <26b88035-b377-a594-0b7b-cfcf25e43e57@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAKTCnzm7jB1doPjySSjBe6B6YhTOkU+Cm+DJA94PQ7rNyXpx4Q@mail.gmail.com>

Hello:

On 06/14/2017 12:27 AM, Balbir Singh wrote:
> On Wed, Jun 14, 2017 at 3:25 PM, Balbir Singh <bsingharora@gmail.com> wrote:
>>
>>
>> On Wed, Jun 14, 2017 at 8:21 AM, Michael Bringmann <mwb@linux.vnet.ibm.com>
>> wrote:
>>>
>>> On a related note, we are discussing the addition of 2 new device-tree
>>> properties
>>> with Pete Heyrman and his fellows that should simplify the determination
>>> of the
>>> set of required nodes.
>>>
>>> * One property would provide the total/max number of nodes needed by the
>>> kernel
>>>   on the current hardware.
>>
>>
> 
> Yes, that would be nice to have
> 
>>
>>>
>>> * A second property would provide the total/max number of nodes that the
>>> kernel
>>>   could use on any system to which it could be migrated.
>>>
>>
> 
> Not sure about this one, are you suggesting more memory can be added
> depending on the migration target?

We would use only one of these numbers to allocate nodes.  I have only been
on the periphery of the discussions, so I can not communicate the full
reasoning as to why both measures would be needed.  We would like to have
the first number for node allocation/initialization, but if only the second
value were provided, we would likely need to use it.

>>
>>
>>>
>>> These properties aren't available, yet, and it takes time to define new
>>> properties
>>> in the PAPR and have them implemented in pHyp and the kernel.  As an
>>> intermediary
>>> step, the systems which are doing a lot of dynamic hot-add/hot-remove
>>> configuration
>>> could provide equivalent information to the PowerPC kernel with a command
>>> line
>>> parameter.  The 'numa.c' code would then read this value and fill in the
>>> necessary
>>> entries in the 'node_possible_map'.
>>>
>>> Would you foresee any problems with using such a feature?
>>
>>
> 
> Sorry my mailer goofed up, resending
> 
> Balbir Singh
> 

Thanks.


-- 
Michael W. Bringmann
Linux Technology Center
IBM Corporation
Tie-Line  363-5196
External: (512) 286-5196
Cell:       (512) 466-0650
mwb@linux.vnet.ibm.com

  reply	other threads:[~2017-06-14 13:41 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 15:15 [Patch 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc Michael Bringmann
2017-05-23 15:52 ` Reza Arbab
2017-05-23 20:05   ` Michael Bringmann
2017-05-23 21:49     ` Reza Arbab
2017-05-23 22:41       ` Michael Bringmann
2017-05-23 22:44       ` Michael Bringmann
2017-05-24 11:19         ` Michael Ellerman
2017-05-24 23:55           ` Michael Bringmann
2017-05-25  6:19             ` Michael Ellerman
2017-05-25 13:40               ` Michael Bringmann
2017-05-25 15:10               ` Reza Arbab
2017-05-25 15:26                 ` Michael Bringmann
2017-05-26  3:46                 ` Balbir Singh
2017-05-26  3:46                 ` Michael Ellerman
2017-05-26 12:31                   ` Michael Bringmann
2017-05-26 14:31                   ` Reza Arbab
2017-05-29  5:32                     ` Michael Ellerman
2017-05-31 14:05                       ` Michael Bringmann
2017-06-01  9:36                         ` Michael Ellerman
2017-06-01 21:33                           ` Reza Arbab
2017-06-07  8:06                             ` Balbir Singh
2017-06-07 12:07                             ` Michael Ellerman
2017-06-02  5:24                           ` Michael Bringmann
2017-06-06  9:48                             ` Michael Ellerman
2017-06-06 16:16                               ` Michael Bringmann
2017-06-07 12:08                                 ` Michael Ellerman
2017-06-07 17:28                                   ` RESEND " Michael Bringmann
2017-06-13 10:45                                     ` Michael Ellerman
2017-06-13 22:21                                       ` Michael Bringmann
2017-06-14  5:25                                         ` Balbir Singh
2017-06-14  5:27                                           ` Balbir Singh
2017-06-14 13:41                                             ` Michael Bringmann [this message]
2017-06-07 17:17                                 ` Michael Bringmann
2017-05-24 14:36         ` Reza Arbab
2017-05-24 23:41           ` Michael Bringmann

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=26b88035-b377-a594-0b7b-cfcf25e43e57@linux.vnet.ibm.com \
    --to=mwb@linux.vnet.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=arbab@linux.vnet.ibm.com \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=bigeasy@linutronix.de \
    --cc=bsingharora@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mbringm@us.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.org \
    --cc=shailendras@nvidia.com \
    --cc=tglx@linutronix.de \
    /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).