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

On 20.07.23 09:14, 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 the memmap for this new memory. It'

Re: [PATCH RESEND 1/4] memory tiering: add abstract distance calculation algorithms management

"Huang, Ying" writes: > Hi, Alistair, > > Thanks a lot for comments! > > Alistair Popple writes: > >> Huang Ying writes: >> >>> The abstract distance may be calculated by various drivers, such as >>> ACPI HMAT, CXL CDAT, etc. While it may be used by various code which >>> hot-add memory node

Re: [PATCH RESEND 4/4] dax, kmem: calculate abstract distance with general interface

Alistair Popple writes: > Huang Ying writes: > >> Previously, a fixed abstract distance MEMTIER_DEFAULT_DAX_ADISTANCE is >> used for slow memory type in kmem driver. This limits the usage of >> kmem driver, for example, it cannot be used for HBM (high bandwidth >> memory). >> >> So, we use the