[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181119162942.25qyec52mtzwe2xo@ca-dmjordan1.us.oracle.com>
Date: Mon, 19 Nov 2018 08:29:42 -0800
From: Daniel Jordan <daniel.m.jordan@...cle.com>
To: "Elliott, Robert (Persistent Memory)" <elliott@....com>
Cc: Daniel Jordan <daniel.m.jordan@...cle.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"aarcange@...hat.com" <aarcange@...hat.com>,
"aaron.lu@...el.com" <aaron.lu@...el.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"alex.williamson@...hat.com" <alex.williamson@...hat.com>,
"bsd@...hat.com" <bsd@...hat.com>,
"darrick.wong@...cle.com" <darrick.wong@...cle.com>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"jgg@...lanox.com" <jgg@...lanox.com>,
"jwadams@...gle.com" <jwadams@...gle.com>,
"jiangshanlai@...il.com" <jiangshanlai@...il.com>,
"mhocko@...nel.org" <mhocko@...nel.org>,
"mike.kravetz@...cle.com" <mike.kravetz@...cle.com>,
"Pavel.Tatashin@...rosoft.com" <Pavel.Tatashin@...rosoft.com>,
"prasad.singamsetty@...cle.com" <prasad.singamsetty@...cle.com>,
"rdunlap@...radead.org" <rdunlap@...radead.org>,
"steven.sistare@...cle.com" <steven.sistare@...cle.com>,
"tim.c.chen@...el.com" <tim.c.chen@...el.com>,
"tj@...nel.org" <tj@...nel.org>, "vbabka@...e.cz" <vbabka@...e.cz>,
zwisler@...gle.com
Subject: Re: [RFC PATCH v4 11/13] mm: parallelize deferred struct page
initialization within each node
On Mon, Nov 12, 2018 at 08:54:12AM -0800, Daniel Jordan wrote:
> On Sat, Nov 10, 2018 at 03:48:14AM +0000, Elliott, Robert (Persistent Memory) wrote:
> > > -----Original Message-----
> > > From: linux-kernel-owner@...r.kernel.org <linux-kernel-
> > > owner@...r.kernel.org> On Behalf Of Daniel Jordan
> > > Sent: Monday, November 05, 2018 10:56 AM
> > > Subject: [RFC PATCH v4 11/13] mm: parallelize deferred struct page
> > > initialization within each node
> > >
> > > ... The kernel doesn't
> > > know the memory bandwidth of a given system to get the most efficient
> > > number of threads, so there's some guesswork involved.
> >
> > The ACPI HMAT (Heterogeneous Memory Attribute Table) is designed to report
> > that kind of information, and could facilitate automatic tuning.
> >
> > There was discussion last year about kernel support for it:
> > https://lore.kernel.org/lkml/20171214021019.13579-1-ross.zwisler@linux.intel.com/
>
> Thanks for bringing this up. I'm traveling but will take a closer look when I
> get back.
So this series would give the total bandwidth for a memory target, but there's
not a way to map that to a CPU count. In other words, it seems we couldn't
determine how many CPUs it takes to reach the max bandwidth. If I haven't
missed something, I'm going to remove that comment.
Powered by blists - more mailing lists