On Mon, 13 Jun 2016 15:53:02 +0200
Peter Zijlstra wrote:
> On Mon, Jun 13, 2016 at 03:19:42PM +0200, Martin Schwidefsky wrote:
> > On Mon, 13 Jun 2016 15:06:47 +0200
> > Peter Zijlstra wrote:
> >
> > > On Mon, Jun 13, 2016 at 01:22:30PM +0200, Heiko
On Mon, 13 Jun 2016 15:53:02 +0200
Peter Zijlstra wrote:
> On Mon, Jun 13, 2016 at 03:19:42PM +0200, Martin Schwidefsky wrote:
> > On Mon, 13 Jun 2016 15:06:47 +0200
> > Peter Zijlstra wrote:
> >
> > > On Mon, Jun 13, 2016 at 01:22:30PM +0200, Heiko Carstens wrote:
> > > > Yes, and actually we
On Mon, Jun 13, 2016 at 03:19:42PM +0200, Martin Schwidefsky wrote:
> On Mon, 13 Jun 2016 15:06:47 +0200
> Peter Zijlstra 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
On Mon, Jun 13, 2016 at 03:19:42PM +0200, Martin Schwidefsky wrote:
> On Mon, 13 Jun 2016 15:06:47 +0200
> Peter Zijlstra 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
> > >
On Mon, 13 Jun 2016 15:06:47 +0200
Peter Zijlstra 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
On Mon, 13 Jun 2016 15:06:47 +0200
Peter Zijlstra 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
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.
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.
On Mon, Jun 13, 2016 at 01:06:21PM +0200, Peter Zijlstra wrote:
> On Wed, Jun 08, 2016 at 11:09:16AM +0200, Heiko Carstens wrote:
> > The z13 machine added a fourth level to the cpu topology
> > information. The new top level is called drawer.
> >
> > A drawer contains two books, which used to be
On Mon, Jun 13, 2016 at 01:06:21PM +0200, Peter Zijlstra wrote:
> On Wed, Jun 08, 2016 at 11:09:16AM +0200, Heiko Carstens wrote:
> > The z13 machine added a fourth level to the cpu topology
> > information. The new top level is called drawer.
> >
> > A drawer contains two books, which used to be
On Mon, Jun 13, 2016 at 01:25:53PM +0200, Heiko Carstens wrote:
> On Mon, Jun 13, 2016 at 01:06:21PM +0200, Peter Zijlstra wrote:
> > On Wed, Jun 08, 2016 at 11:09:16AM +0200, Heiko Carstens wrote:
> > > The z13 machine added a fourth level to the cpu topology
> > > information. The new top level
On Mon, Jun 13, 2016 at 01:25:53PM +0200, Heiko Carstens wrote:
> On Mon, Jun 13, 2016 at 01:06:21PM +0200, Peter Zijlstra wrote:
> > On Wed, Jun 08, 2016 at 11:09:16AM +0200, Heiko Carstens wrote:
> > > The z13 machine added a fourth level to the cpu topology
> > > information. The new top level
On Mon, Jun 13, 2016 at 01:06:21PM +0200, Peter Zijlstra wrote:
> On Wed, Jun 08, 2016 at 11:09:16AM +0200, Heiko Carstens wrote:
> > The z13 machine added a fourth level to the cpu topology
> > information. The new top level is called drawer.
> >
> > A drawer contains two books, which used to be
On Mon, Jun 13, 2016 at 01:06:21PM +0200, Peter Zijlstra wrote:
> On Wed, Jun 08, 2016 at 11:09:16AM +0200, Heiko Carstens wrote:
> > The z13 machine added a fourth level to the cpu topology
> > information. The new top level is called drawer.
> >
> > A drawer contains two books, which used to be
On Wed, Jun 08, 2016 at 11:09:16AM +0200, Heiko Carstens wrote:
> The z13 machine added a fourth level to the cpu topology
> information. The new top level is called drawer.
>
> A drawer contains two books, which used to be the top level.
>
> Adding this additional scheduling domain did show
On Wed, Jun 08, 2016 at 11:09:16AM +0200, Heiko Carstens wrote:
> The z13 machine added a fourth level to the cpu topology
> information. The new top level is called drawer.
>
> A drawer contains two books, which used to be the top level.
>
> Adding this additional scheduling domain did show
The z13 machine added a fourth level to the cpu topology
information. The new top level is called drawer.
A drawer contains two books, which used to be the top level.
Adding this additional scheduling domain did show performance
improvements for some workloads of up to 8%, while there don't
seem
The z13 machine added a fourth level to the cpu topology
information. The new top level is called drawer.
A drawer contains two books, which used to be the top level.
Adding this additional scheduling domain did show performance
improvements for some workloads of up to 8%, while there don't
seem
18 matches
Mail list logo