mm-vmalloc-use-trace_purge_vmap_area_lazy-event.patch removed from -mm tree
The quilt patch titled
Subject: mm: vmalloc: use trace_purge_vmap_area_lazy event
has been removed from the -mm tree. Its filename was
mm-vmalloc-use-trace_purge_vmap_area_lazy-event.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: "Uladzislau Rezki (Sony)" <[email protected]>
Subject: mm: vmalloc: use trace_purge_vmap_area_lazy event
Date: Tue, 18 Oct 2022 20:10:51 +0200
This is for debug purposes and is called when all outstanding areas are removed back to the vmap space. It gives some extra information about:
- a start:end range where set of vmap ares were freed;
- a number of purged areas which were backed off.
---
mm/vmalloc.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)
mm/vmalloc.c renamed from mm/vmalloc.c~mm-vmalloc-use-trace_purge_vmap_area_lazy-event +7 -2
@@ -1730,6 +1730,7 @@ static void purge_fragmented_blocks_allcstatic bool __purge_vmap_area_lazy (unsigned long start,unsigned long end) {unsigned long resched_threshold; +unsigned int num_purged_areas =0 ;struct list_head local_purge_list;struct vmap_area *va, *n_va;
@@ -1741,7 +1742,7 @@ static bool __purge_vmap_area_lazy(unsigspin_unlock (&purge_vmap_area_lock);if (unlikely (list_empty (&local_purge_list))) -return false; + goto out; start = min(start, list_first_entry(&local_purge_list,
@@ -1776,12 +1777,16 @@ static bool __purge_vmap_area_lazy(unsig va->va_start, va->va_end);atomic_long_sub (nr, &vmap_lazy_nr); + num_purged_areas++;if (atomic_long_read (&vmap_lazy_nr) < resched_threshold)cond_resched_lock (&free_vmap_area_lock); }spin_unlock (&free_vmap_area_lock); -return true; + +out: +trace_purge_vmap_area_lazy (start, end, num_purged_areas); +return num_purged_areas >0 ; }/*
_
Patches currently in -mm which might be from [email protected] are