Re: [PATCH 0/3] mm: use memmap_on_memory semantics for dax/kmem

2023-07-14 Thread Jeff Moyer
David Hildenbrand writes: > On 13.07.23 21:12, Jeff Moyer wrote: >> David Hildenbrand writes: >> >>> On 16.06.23 00:00, Vishal Verma wrote: The dax/kmem driver can potentially hot-add large amounts of memory originating from CXL memory expanders, or NVDIMMs, or other 'device memor

Re: [PATCH 0/3] mm: use memmap_on_memory semantics for dax/kmem

2023-07-14 Thread David Hildenbrand
On 13.07.23 21:12, Jeff Moyer wrote: David Hildenbrand writes: On 16.06.23 00:00, Vishal Verma wrote: The dax/kmem driver can potentially hot-add large amounts of memory originating from CXL memory expanders, or NVDIMMs, or other 'device memories'. There is a chance there isn't enough regular

Re: [PATCH 0/3] mm: use memmap_on_memory semantics for dax/kmem

2023-07-13 Thread Jeff Moyer
David Hildenbrand writes: > On 16.06.23 00:00, Vishal Verma wrote: >> The dax/kmem driver can potentially hot-add large amounts of memory >> originating from CXL memory expanders, or NVDIMMs, or other 'device >> memories'. There is a chance there isn't enough regular system memory >> available to

Re: [PATCH 0/3] mm: use memmap_on_memory semantics for dax/kmem

2023-06-22 Thread David Hildenbrand
On 21.06.23 21:32, Verma, Vishal L wrote: On Fri, 2023-06-16 at 09:44 +0200, David Hildenbrand wrote: On 16.06.23 00:00, Vishal Verma wrote: The dax/kmem driver can potentially hot-add large amounts of memory originating from CXL memory expanders, or NVDIMMs, or other 'device memories'. There i

Re: [PATCH 0/3] mm: use memmap_on_memory semantics for dax/kmem

2023-06-21 Thread Verma, Vishal L
On Fri, 2023-06-16 at 09:44 +0200, David Hildenbrand wrote: > On 16.06.23 00:00, Vishal Verma wrote: > > The dax/kmem driver can potentially hot-add large amounts of memory > > originating from CXL memory expanders, or NVDIMMs, or other 'device > > memories'. There is a chance there isn't enough re

Re: [PATCH 0/3] mm: use memmap_on_memory semantics for dax/kmem

2023-06-16 Thread David Hildenbrand
On 16.06.23 00:00, Vishal Verma wrote: The dax/kmem driver can potentially hot-add large amounts of memory originating from CXL memory expanders, or NVDIMMs, or other 'device memories'. There is a chance there isn't enough regular system memory available to fit ythe memmap for this new memory. It

[PATCH 0/3] mm: use memmap_on_memory semantics for dax/kmem

2023-06-15 Thread Vishal Verma
The dax/kmem driver can potentially hot-add large amounts of memory originating from CXL memory expanders, or NVDIMMs, or other 'device memories'. There is a chance there isn't enough regular system memory available to fit ythe memmap for this new memory. It's therefore desirable, if all other cond