search for: pingfan

...r at suse.de> > Cc: Mel Gorman <mgorman at techsingularity.net> > Cc: Mike Rapoport <rppt at linux.ibm.com> > Cc: Dan Williams <dan.j.williams at intel.com> > Cc: Anshuman Khandual <anshuman.khandual at arm.com> > Cc: Qian Cai <cai at lca.pw> > Cc: Pingfan Liu <kernelfans at gmail.com> > Signed-off-by: David Hildenbrand <david at redhat.com> Looks good to me. Thanks for dropping __put_page hooks! Acked-by: Michal Hocko <mhocko at suse.com> > --- > include/linux/page-flags.h | 10 +++++++++ > mm/memory_hotplug.c...

...c: Oscar Salvador <osalvador at suse.de> Cc: Mel Gorman <mgorman at techsingularity.net> Cc: Mike Rapoport <rppt at linux.ibm.com> Cc: Dan Williams <dan.j.williams at intel.com> Cc: Anshuman Khandual <anshuman.khandual at arm.com> Cc: Qian Cai <cai at lca.pw> Cc: Pingfan Liu <kernelfans at gmail.com> Signed-off-by: David Hildenbrand <david at redhat.com> --- include/linux/page-flags.h | 10 +++++++++ mm/memory_hotplug.c | 44 +++++++++++++++++++++++++++++--------- mm/page_alloc.c | 24 +++++++++++++++++++++ mm/page_isolation.c...

...c: Oscar Salvador <osalvador at suse.de> Cc: Mel Gorman <mgorman at techsingularity.net> Cc: Mike Rapoport <rppt at linux.ibm.com> Cc: Dan Williams <dan.j.williams at intel.com> Cc: Anshuman Khandual <anshuman.khandual at arm.com> Cc: Qian Cai <cai at lca.pw> Cc: Pingfan Liu <kernelfans at gmail.com> Signed-off-by: David Hildenbrand <david at redhat.com> --- include/linux/page-flags.h | 10 +++++++++ mm/memory_hotplug.c | 44 +++++++++++++++++++++++++++++--------- mm/page_alloc.c | 24 +++++++++++++++++++++ mm/page_isolation.c...

...c: Oscar Salvador <osalvador at suse.de> Cc: Mel Gorman <mgorman at techsingularity.net> Cc: Mike Rapoport <rppt at linux.ibm.com> Cc: Dan Williams <dan.j.williams at intel.com> Cc: Anshuman Khandual <anshuman.khandual at arm.com> Cc: Qian Cai <cai at lca.pw> Cc: Pingfan Liu <kernelfans at gmail.com> Signed-off-by: David Hildenbrand <david at redhat.com> --- include/linux/page-flags.h | 10 +++++++++ mm/memory_hotplug.c | 44 +++++++++++++++++++++++++++++--------- mm/page_alloc.c | 24 +++++++++++++++++++++ mm/page_isolation.c...

...r at suse.de> > Cc: Mel Gorman <mgorman at techsingularity.net> > Cc: Mike Rapoport <rppt at linux.ibm.com> > Cc: Dan Williams <dan.j.williams at intel.com> > Cc: Anshuman Khandual <anshuman.khandual at arm.com> > Cc: Qian Cai <cai at lca.pw> > Cc: Pingfan Liu <kernelfans at gmail.com> > Signed-off-by: David Hildenbrand <david at redhat.com> Andrew, could you please ack merging this through the vhost tree together with the rest of the patches? > --- > include/linux/page-flags.h | 10 +++++++++ > mm/memory_hotplug.c...

...Duyck <alexander.h.duyck at linux.intel.com> Cc: Anthony Yznaga <anthony.yznaga at oracle.com> Cc: Vlastimil Babka <vbabka at suse.cz> Cc: Johannes Weiner <hannes at cmpxchg.org> Cc: Oscar Salvador <osalvador at suse.de> Cc: Michal Hocko <mhocko at suse.com> Cc: Pingfan Liu <kernelfans at gmail.com> Cc: Qian Cai <cai at lca.pw> Cc: Dan Williams <dan.j.williams at intel.com> Cc: Mel Gorman <mgorman at techsingularity.net> Cc: Mike Rapoport <rppt at linux.vnet.ibm.com> Cc: Wei Yang <richardw.yang at linux.intel.com> Cc: Alexander...

...t;mst at redhat.com> Cc: Jason Wang <jasowang at redhat.com> Cc: Boris Ostrovsky <boris.ostrovsky at oracle.com> Cc: Juergen Gross <jgross at suse.com> Cc: Stefano Stabellini <sstabellini at kernel.org> Cc: "Oliver O'Halloran" <oohall at gmail.com> Cc: Pingfan Liu <kernelfans at gmail.com> Cc: Nathan Lynch <nathanl at linux.ibm.com> Cc: Libor Pechacek <lpechacek at suse.cz> Cc: Anton Blanchard <anton at ozlabs.org> Cc: Leonardo Bras <leobras.c at gmail.com> Cc: linuxppc-dev at lists.ozlabs.org Cc: linux-acpi at vger.kernel.o...

...t;mst at redhat.com> Cc: Jason Wang <jasowang at redhat.com> Cc: Boris Ostrovsky <boris.ostrovsky at oracle.com> Cc: Juergen Gross <jgross at suse.com> Cc: Stefano Stabellini <sstabellini at kernel.org> Cc: "Oliver O'Halloran" <oohall at gmail.com> Cc: Pingfan Liu <kernelfans at gmail.com> Cc: Nathan Lynch <nathanl at linux.ibm.com> Cc: Libor Pechacek <lpechacek at suse.cz> Cc: Anton Blanchard <anton at ozlabs.org> Cc: Leonardo Bras <leobras.c at gmail.com> Cc: linuxppc-dev at lists.ozlabs.org Cc: linux-acpi at vger.kernel.o...

On Wed 23-10-19 12:03:51, David Hildenbrand wrote: > >Do you see any downsides? > > The only downside I see is that we get more false negatives on > has_unmovable_pages(), eventually resulting in the offlining stage after > isolation to loop forever (as some PageOffline() pages are not movable > (especially, XEN balloon, HyperV balloon), there won't be progress). >

On Wed 23-10-19 12:03:51, David Hildenbrand wrote: > >Do you see any downsides? > > The only downside I see is that we get more false negatives on > has_unmovable_pages(), eventually resulting in the offlining stage after > isolation to loop forever (as some PageOffline() pages are not movable > (especially, XEN balloon, HyperV balloon), there won't be progress). >

This is the follow up of [1]: [PATCH v1 0/3] mm/memory_hotplug: Make virtio-mem play nicely with kexec-tools I realized that this is not only helpful for virtio-mem, but also for dax/kmem - it's a fix for that use case (see patch #3) of persistent memory. Also, while testing, I discovered that kexec-tools will *not* add dax/kmem memory (anything not directly under the root when parsing

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where

This series is based on [1]: [PATCH v2 00/10] virtio-mem: paravirtualized memory That will hopefull get picked up soon, rebased to -next. The following patches were reverted from -next [2]: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use As discussed in that thread, they should be reverted from -next already. In theory, if people agree, we could take the first two patches

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-v2 I now have acks for all !virtio-mem changes. I'll be happy to get review feedback, testing reports, etc. for the virtio-mem changes. If there are no further comments, I guess this is good to go as a v1 soon. The basic idea of virtio-mem is to provide a

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-v3 Patch #1 - #10 where contained in v2 and only contain minor modifications (mostly smaller fixes). The remaining patches are new and contain smaller optimizations. Details about virtio-mem can be found in the cover letter of v2 [1]. A basic QEMU implementation was

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-v3 Patch #1 - #10 where contained in v2 and only contain minor modifications (mostly smaller fixes). The remaining patches are new and contain smaller optimizations. Details about virtio-mem can be found in the cover letter of v2 [1]. A basic QEMU implementation was