Re: [PATCH 0/7] libnvdimm/pfn: Fix section-alignment padding

2019-02-20 Thread Jeff Moyer
Dan Williams writes: > On Tue, Feb 12, 2019 at 1:37 PM Dan Williams wrote: >> >> Lately Linux has encountered platforms that collide Persistent Memory >> regions between each other, specifically cases where ->start_pad needed >> to be non-zero. This lead to commit ae86cbfef381 "libnvdimm, pfn:

Re: [PATCH 0/7] libnvdimm/pfn: Fix section-alignment padding

2019-02-20 Thread Johannes Thumshirn
On 20/02/2019 18:11, Dan Williams wrote: > Hello valued reviewers, can I plead for a sanity check of at least > "libnvdimm/pfn: Introduce super-block minimum version requirements" > and "libnvdimm/pfn: Fix 'start_pad' implementation"? In particular > Jeff / Johannes this has end user / distro

Re: [PATCH 0/7] libnvdimm/pfn: Fix section-alignment padding

2019-02-20 Thread Dan Williams
On Tue, Feb 12, 2019 at 1:37 PM Dan Williams wrote: > > Lately Linux has encountered platforms that collide Persistent Memory > regions between each other, specifically cases where ->start_pad needed > to be non-zero. This lead to commit ae86cbfef381 "libnvdimm, pfn: Pad > pfn namespaces relative

[PATCH 0/7] libnvdimm/pfn: Fix section-alignment padding

2019-02-12 Thread Dan Williams
Lately Linux has encountered platforms that collide Persistent Memory regions between each other, specifically cases where ->start_pad needed to be non-zero. This lead to commit ae86cbfef381 "libnvdimm, pfn: Pad pfn namespaces relative to other regions". That commit allowed namespaces to be mapped