mm/vmalloc.c: add priority threshold to __purge_vmap_area_lazy()
authorUladzislau Rezki (Sony) <>
Tue, 14 May 2019 22:41:22 +0000 (15:41 -0700)
committerLinus Torvalds <>
Wed, 15 May 2019 02:52:48 +0000 (19:52 -0700)
Commit 763b218ddfaf ("mm: add preempt points into __purge_vmap_area_lazy()")
introduced some preempt points, one of those is making an allocation
more prioritized over lazy free of vmap areas.

Prioritizing an allocation over freeing does not work well all the time,
i.e.  it should be rather a compromise.

1) Number of lazy pages directly influences the busy list length thus
   on operations like: allocation, lookup, unmap, remove, etc.

2) Under heavy stress of vmalloc subsystem I run into a situation when
   memory usage gets increased hitting out_of_memory -> panic state due to
   completely blocking of logic that frees vmap areas in the
   __purge_vmap_area_lazy() function.

Establish a threshold passing which the freeing is prioritized back over
allocation creating a balance between each other.

Using vmalloc test driver in "stress mode", i.e.  When all available
test cases are run simultaneously on all online CPUs applying a
pressure on the vmalloc subsystem, my HiKey 960 board runs out of
memory due to the fact that __purge_vmap_area_lazy() logic simply is
not able to free pages in time.

How I run it:

1) You should build your kernel with CONFIG_TEST_VMALLOC=m
2) ./tools/testing/selftests/vm/ stress

During this test "vmap_lazy_nr" pages will go far beyond acceptable
lazy_max_pages() threshold, that will lead to enormous busy list size
and other problems including allocation time and so on.

Signed-off-by: Uladzislau Rezki (Sony) <>
Reviewed-by: Andrew Morton <>
Cc: Michal Hocko <>
Cc: Matthew Wilcox <>
Cc: Thomas Garnier <>
Cc: Oleksiy Avramchenko <>
Cc: Steven Rostedt <>
Cc: Joel Fernandes <>
Cc: Thomas Gleixner <>
Cc: Ingo Molnar <>
Cc: Tejun Heo <>
Cc: Joel Fernandes <>
Signed-off-by: Andrew Morton <>
Signed-off-by: Linus Torvalds <>

index e5e9e1fcac014b5ad8c98da2f807259ad70754de..072c8e0df90a0a16e95bdfe18e2eec380e24f7d5 100644 (file)
@@ -662,23 +662,27 @@ static bool __purge_vmap_area_lazy(unsigned long start, unsigned long end)
        struct llist_node *valist;
        struct vmap_area *va;
        struct vmap_area *n_va;
-       bool do_free = false;
+       int resched_threshold;
        valist = llist_del_all(&vmap_purge_list);
+       if (unlikely(valist == NULL))
+               return false;
+       /*
+        * TODO: to calculate a flush range without looping.
+        * The list can be up to lazy_max_pages() elements.
+        */
        llist_for_each_entry(va, valist, purge_list) {
                if (va->va_start < start)
                        start = va->va_start;
                if (va->va_end > end)
                        end = va->va_end;
-               do_free = true;
-       if (!do_free)
-               return false;
        flush_tlb_kernel_range(start, end);
+       resched_threshold = (int) lazy_max_pages() << 1;
        llist_for_each_entry_safe(va, n_va, valist, purge_list) {
@@ -686,7 +690,9 @@ static bool __purge_vmap_area_lazy(unsigned long start, unsigned long end)
                atomic_sub(nr, &vmap_lazy_nr);
-               cond_resched_lock(&vmap_area_lock);
+               if (atomic_read(&vmap_lazy_nr) < resched_threshold)
+                       cond_resched_lock(&vmap_area_lock);
        return true;