RE: [RFC PATCH 0/6] decrease unnecessary gap due to pmem kmem alignment

2020-07-29 Thread Justin He
nkaj Gupta > ; Ira Weiny ; Kaly Xin > > Subject: Re: [RFC PATCH 0/6] decrease unnecessary gap due to pmem kmem > alignment > > On 29.07.20 11:31, Mike Rapoport wrote: > > Hi Justin, > > > > On Wed, Jul 29, 2020 at 08:27:58AM +, Justin He wrote: > >>

Re: [RFC PATCH 0/6] decrease unnecessary gap due to pmem kmem alignment

2020-07-29 Thread Mike Rapoport
On Wed, Jul 29, 2020 at 03:03:04PM +0200, David Hildenbrand wrote: > On 29.07.20 15:00, Mike Rapoport wrote: > > On Wed, Jul 29, 2020 at 11:35:20AM +0200, David Hildenbrand wrote: > >>> > >>> There is still large gap with ARM64_64K_PAGES, though. > >>> > >>> As for SPARSEMEM without VMEMMAP, are

Re: [RFC PATCH 0/6] decrease unnecessary gap due to pmem kmem alignment

2020-07-29 Thread David Hildenbrand
On 29.07.20 15:00, Mike Rapoport wrote: > On Wed, Jul 29, 2020 at 11:35:20AM +0200, David Hildenbrand wrote: >> On 29.07.20 11:31, Mike Rapoport wrote: >>> Hi Justin, >>> >>> On Wed, Jul 29, 2020 at 08:27:58AM +, Justin He wrote: Hi David >> >> Without this series, if qemu creates

Re: [RFC PATCH 0/6] decrease unnecessary gap due to pmem kmem alignment

2020-07-29 Thread Mike Rapoport
On Wed, Jul 29, 2020 at 11:35:20AM +0200, David Hildenbrand wrote: > On 29.07.20 11:31, Mike Rapoport wrote: > > Hi Justin, > > > > On Wed, Jul 29, 2020 at 08:27:58AM +, Justin He wrote: > >> Hi David > > Without this series, if qemu creates a 4G bytes nvdimm device, we can > >>> onl

Re: [RFC PATCH 0/6] decrease unnecessary gap due to pmem kmem alignment

2020-07-29 Thread David Hildenbrand
On 29.07.20 11:31, Mike Rapoport wrote: > Hi Justin, > > On Wed, Jul 29, 2020 at 08:27:58AM +, Justin He wrote: >> Hi David Without this series, if qemu creates a 4G bytes nvdimm device, we can >>> only use 2G bytes for dax pmem(kmem) in the worst case. e.g. 24000-

Re: [RFC PATCH 0/6] decrease unnecessary gap due to pmem kmem alignment

2020-07-29 Thread Mike Rapoport
Hi Justin, On Wed, Jul 29, 2020 at 08:27:58AM +, Justin He wrote: > Hi David > > > > > > Without this series, if qemu creates a 4G bytes nvdimm device, we can > > only > > > use 2G bytes for dax pmem(kmem) in the worst case. > > > e.g. > > > 24000-33fdf : Persistent Memory > > > We can

Re: [RFC PATCH 0/6] decrease unnecessary gap due to pmem kmem alignment

2020-07-29 Thread David Hildenbrand
inux-arm-ker...@lists.infradead.org; linux- >> ker...@vger.kernel.org; linux-nvd...@lists.01.org; linux...@kvack.org; Wei >> Yang ; Pankaj Gupta >> ; Ira Weiny ; Kaly Xin >> >> Subject: Re: [RFC PATCH 0/6] decrease unnecessary gap due to pmem kmem >> alignment &g

RE: [RFC PATCH 0/6] decrease unnecessary gap due to pmem kmem alignment

2020-07-29 Thread Justin He
...@kvack.org; Wei > Yang ; Pankaj Gupta > ; Ira Weiny ; Kaly Xin > > Subject: Re: [RFC PATCH 0/6] decrease unnecessary gap due to pmem kmem > alignment > > > > > Am 29.07.2020 um 05:35 schrieb Jia He : > > > > When enabling dax pmem as RAM devic

Re: [RFC PATCH 0/6] decrease unnecessary gap due to pmem kmem alignment

2020-07-28 Thread David Hildenbrand
> Am 29.07.2020 um 05:35 schrieb Jia He : > > When enabling dax pmem as RAM device on arm64, I noticed that kmem_start > addr in dev_dax_kmem_probe() should be aligned w/ SECTION_SIZE_BITS(30),i.e. > 1G memblock size. Even Dan Williams' sub-section patch series [1] had been > upstream merged,