Re: [PATCH 3/3] resource: Introduce resource cache

2019-06-20 Thread Dan Williams
On Thu, Jun 20, 2019 at 2:31 PM Andi Kleen wrote: > > Dan Williams writes: > > > > The underlying issue is that the x86-PAT implementation wants to > > ensure that conflicting mappings are not set up for the same physical > > address. This is mentioned in the developer manuals as problematic on >

Re: [PATCH 3/3] resource: Introduce resource cache

2019-06-20 Thread Andi Kleen
Dan Williams writes: > > The underlying issue is that the x86-PAT implementation wants to > ensure that conflicting mappings are not set up for the same physical > address. This is mentioned in the developer manuals as problematic on > some cpus. Andi, is lookup_memtype() and track_pfn_insert() st

Re: [PATCH 3/3] resource: Introduce resource cache

2019-06-19 Thread Dan Williams
[ add Andi ] On Wed, Jun 19, 2019 at 6:00 AM Bjorn Helgaas wrote: > > On Tue, Jun 18, 2019 at 12:40 AM Nadav Amit wrote: > > > > > On Jun 17, 2019, at 10:33 PM, Nadav Amit wrote: > > > > > >> On Jun 17, 2019, at 9:57 PM, Andrew Morton > > >> wrote: > > >> > > >> On Wed, 12 Jun 2019 21:59:03 -

Re: [PATCH 3/3] resource: Introduce resource cache

2019-06-19 Thread Nadav Amit
> On Jun 19, 2019, at 6:00 AM, Bjorn Helgaas wrote: > > On Tue, Jun 18, 2019 at 12:40 AM Nadav Amit wrote: >>> On Jun 17, 2019, at 10:33 PM, Nadav Amit wrote: >>> On Jun 17, 2019, at 9:57 PM, Andrew Morton wrote: On Wed, 12 Jun 2019 21:59:03 -0700 Nadav Amit wrote:

Re: [PATCH 3/3] resource: Introduce resource cache

2019-06-19 Thread Bjorn Helgaas
On Tue, Jun 18, 2019 at 12:40 AM Nadav Amit wrote: > > > On Jun 17, 2019, at 10:33 PM, Nadav Amit wrote: > > > >> On Jun 17, 2019, at 9:57 PM, Andrew Morton > >> wrote: > >> > >> On Wed, 12 Jun 2019 21:59:03 -0700 Nadav Amit wrote: > >> > >>> For efficient search of resources, as needed to det

Re: [PATCH 3/3] resource: Introduce resource cache

2019-06-17 Thread Nadav Amit
> On Jun 17, 2019, at 9:57 PM, Andrew Morton wrote: > > On Wed, 12 Jun 2019 21:59:03 -0700 Nadav Amit wrote: > >> For efficient search of resources, as needed to determine the memory >> type for dax page-faults, introduce a cache of the most recently used >> top-level resource. Caching the top-

Re: [PATCH 3/3] resource: Introduce resource cache

2019-06-17 Thread Nadav Amit
> On Jun 17, 2019, at 10:33 PM, Nadav Amit wrote: > >> On Jun 17, 2019, at 9:57 PM, Andrew Morton wrote: >> >> On Wed, 12 Jun 2019 21:59:03 -0700 Nadav Amit wrote: >> >>> For efficient search of resources, as needed to determine the memory >>> type for dax page-faults, introduce a cache of th

Re: [PATCH 3/3] resource: Introduce resource cache

2019-06-17 Thread Andrew Morton
On Wed, 12 Jun 2019 21:59:03 -0700 Nadav Amit wrote: > For efficient search of resources, as needed to determine the memory > type for dax page-faults, introduce a cache of the most recently used > top-level resource. Caching the top-level should be safe as ranges in > that level do not overlap (

Re: [PATCH 3/3] resource: Introduce resource cache

2019-06-17 Thread Nadav Amit
> On Jun 15, 2019, at 3:16 PM, Sasha Levin wrote: > > Hi, > > [This is an automated email] > > This commit has been processed because it contains a "Fixes:" tag, > fixing commit: ff3cc952d3f0 resource: Add remove_resource interface. This commit (Patch 3/3) does not have the “Fixes:” tag (and i

[PATCH 3/3] resource: Introduce resource cache

2019-06-13 Thread Nadav Amit
For efficient search of resources, as needed to determine the memory type for dax page-faults, introduce a cache of the most recently used top-level resource. Caching the top-level should be safe as ranges in that level do not overlap (unlike those of lower levels). Keep the cache per-cpu to avoid