Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1420879

Re: [PATCH 2/2] s390/topology: add drawer scheduling domain level

From Peter Zijlstra <peterz@infradead.org>
Newsgroups linux.kernel
Subject Re: [PATCH 2/2] s390/topology: add drawer scheduling domain level
Date 2016-06-13 16:00 +0200
Message-ID <rJAzl-72E-51@gated-at.bofh.it> (permalink)
References (1 earlier) <rHHOy-6Iz-21@gated-at.bofh.it> <rJxUJ-5uh-1@gated-at.bofh.it> <rJzaa-6dn-23@gated-at.bofh.it> <rJzMS-6In-33@gated-at.bofh.it> <rJA6e-6PL-39@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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.

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH 2/2] s390/topology: add drawer scheduling domain level Peter Zijlstra <peterz@infradead.org> - 2016-06-13 13:10 +0200
  Re: [PATCH 2/2] s390/topology: add drawer scheduling domain level Heiko Carstens <heiko.carstens@de.ibm.com> - 2016-06-13 13:30 +0200
    Re: [PATCH 2/2] s390/topology: add drawer scheduling domain level Peter Zijlstra <peterz@infradead.org> - 2016-06-13 13:40 +0200
  Re: [PATCH 2/2] s390/topology: add drawer scheduling domain level Heiko Carstens <heiko.carstens@de.ibm.com> - 2016-06-13 14:30 +0200
    Re: [PATCH 2/2] s390/topology: add drawer scheduling domain level Peter Zijlstra <peterz@infradead.org> - 2016-06-13 15:10 +0200
      Re: [PATCH 2/2] s390/topology: add drawer scheduling domain level Martin Schwidefsky <schwidefsky@de.ibm.com> - 2016-06-13 15:30 +0200
        Re: [PATCH 2/2] s390/topology: add drawer scheduling domain level Peter Zijlstra <peterz@infradead.org> - 2016-06-13 16:00 +0200
          Re: [PATCH 2/2] s390/topology: add drawer scheduling domain level Martin Schwidefsky <schwidefsky@de.ibm.com> - 2016-06-13 16:40 +0200

csiph-web