All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Larrew <jlarrew@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] rebuild_sched_domains considered dangerous
Date: Mon, 09 May 2011 16:26:22 -0500	[thread overview]
Message-ID: <4DC85BFE.7060900@linux.vnet.ibm.com> (raw)
In-Reply-To: <1303336869.2513.26.camel@pasglop>

[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]

On 04/20/2011 05:01 PM, Benjamin Herrenschmidt wrote:
> On Wed, 2011-04-20 at 12:07 +0200, Peter Zijlstra wrote:
>> On Thu, 2011-03-10 at 15:10 +0100, Peter Zijlstra wrote:
>>>
>>> Also, still waiting to hear from the Power7 folks on how often
>>> they think to rebuild the topology and how they think that makes
>>> sense, afaict Power7 does have actual NUMA nodes unlike s390, so
>>> I'm still not seeing how that's going to work properly at all.
>>
>> Jesse care to answer? I hear from Ben you're responsible for that
>> mess.
>
> "responsible for this mess" is a big word :-)
>
> But he's the one to last play with that code ... Jesse ?
>

Hi Peter!

According the the Power firmware folks, updating the home node of a virtual cpu happens rather infrequently. The VPHN code currently checks for topology updates every 60 seconds, but we can poll less frequently if it helps. I chose 60 second intervals simply because that's how often they check the topology on s390. ;-)

As for updating the memory topology, there are cases where changing the home node of a virtual cpu doesn't affect the memory topology. If it does, there is a separate notification system for memory topology updates that is independent from the cpu updates. I plan to start working on a patch set to enable memory topology updates in the kernel in the coming weeks, but I wanted to get the cpu patches out on the list so we could start having these debates. :)

Sincerely,

Jesse Larrew
Software Engineer, Linux on Power Kernel Team
IBM Linux Technology Center
Phone: (512) 973-2052 (T/L: 363-2052)
jlarrew@linux.vnet.ibm.com


[-- Attachment #2: Type: text/html, Size: 2409 bytes --]

  reply	other threads:[~2011-05-09 21:26 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09  2:58 [BUG] rebuild_sched_domains considered dangerous Benjamin Herrenschmidt
2011-03-09  2:58 ` Benjamin Herrenschmidt
2011-03-09 10:19 ` Peter Zijlstra
2011-03-09 10:19   ` Peter Zijlstra
2011-03-09 11:33   ` Peter Zijlstra
2011-03-09 11:33     ` Peter Zijlstra
2011-03-09 13:15     ` Martin Schwidefsky
2011-03-09 13:15       ` Martin Schwidefsky
2011-03-09 13:19       ` Peter Zijlstra
2011-03-09 13:19         ` Peter Zijlstra
2011-03-09 13:31         ` Martin Schwidefsky
2011-03-09 13:31           ` Martin Schwidefsky
2011-03-09 13:33           ` Peter Zijlstra
2011-03-09 13:33             ` Peter Zijlstra
2011-03-09 13:46             ` Martin Schwidefsky
2011-03-09 13:46               ` Martin Schwidefsky
2011-03-09 13:54               ` Peter Zijlstra
2011-03-09 13:54                 ` Peter Zijlstra
2011-03-09 15:26     ` Steven Rostedt
2011-03-09 15:26       ` Steven Rostedt
2011-03-09 13:01   ` Peter Zijlstra
2011-03-09 13:01     ` Peter Zijlstra
2011-03-10 14:10     ` Peter Zijlstra
2011-03-10 14:10       ` Peter Zijlstra
2011-04-20 10:07       ` Peter Zijlstra
2011-04-20 10:07         ` Peter Zijlstra
2011-04-20 22:01         ` Benjamin Herrenschmidt
2011-04-20 22:01           ` Benjamin Herrenschmidt
2011-05-09 21:26           ` Jesse Larrew [this message]
2011-05-10 14:09             ` Peter Zijlstra
2011-05-10 14:09               ` Peter Zijlstra
2011-05-11 16:17               ` Jesse Larrew
2011-05-11 16:17                 ` Jesse Larrew
2011-06-03 14:47                 ` Peter Zijlstra
2011-06-03 14:47                   ` Peter Zijlstra

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=4DC85BFE.7060900@linux.vnet.ibm.com \
    --to=jlarrew@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=peterz@infradead.org \
    --cc=schwidefsky@de.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.