mm: add priority threshold to __purge_vmap_area_lazy()
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 influence on 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.
Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>