From: Peter Zijlstra <peterz@infradead.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] s390/topology: add drawer scheduling domain level
Date: Mon, 13 Jun 2016 15:53:02 +0200 [thread overview]
Message-ID: <20160613135302.GA30909@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160613151942.02028e15@mschwide>
On Mon, Jun 13, 2016 at 03:19:42PM +0200, Martin Schwidefsky wrote:
> On Mon, 13 Jun 2016 15:06:47 +0200
> Peter Zijlstra <peterz@infradead.org> wrote:
>
> > On Mon, Jun 13, 2016 at 01:22:30PM +0200, Heiko Carstens wrote:
> > > Yes, and actually we are all virt/LPAR always, so this is unfortunately not
> > > very easy to do. And yes, I do agree that for the 1:1 case it most likely
> > > would make sense, however we don't have any run-time guarantee to stay 1:1.
> >
> > One option would be to make it a boot option; such that the
> > administrator has to set it. At that point, if the admin creates
> > multiple LPARs its on him.
>
> Unfortunately not good enough. The LPAR code tries to optimize the layout
> at the time a partition is activated. The landscape of already running
> partitions can change at this point.
Would not the admin _know_ this? It would be him activating partitions
after all, no?
> To get around this you would have to activate *all* partitions first and
> then start the operating systems in a second step.
Arguably, you only care about the single partition covering the entire
machine case, so I don't see that being a problem.
Again, admin _knows_ this.
> And then there is concurrent repair which will move things around if a
> piece of memory goes bad. This happens rarely though.
That would be magic disturbance indeed, nothing much to do about that.
next prev parent reply other threads:[~2016-06-13 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 9:09 [PATCH 0/2] s390: introduce drawer scheduling domain Heiko Carstens
2016-06-08 9:09 ` [PATCH 1/2] topology/sysfs: provide drawer id and siblings attributes Heiko Carstens
2016-06-08 9:09 ` [PATCH 2/2] s390/topology: add drawer scheduling domain level Heiko Carstens
2016-06-13 11:06 ` Peter Zijlstra
2016-06-13 11:22 ` Heiko Carstens
2016-06-13 13:06 ` Peter Zijlstra
2016-06-13 13:19 ` Martin Schwidefsky
2016-06-13 13:53 ` Peter Zijlstra [this message]
2016-06-13 14:37 ` Martin Schwidefsky
2016-06-13 11:25 ` Heiko Carstens
2016-06-13 11:33 ` 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=20160613135302.GA30909@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.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 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).