3 commits

Author	SHA1	Message	Date
Vladimir Kondratyev	2fe9ea5d3a	LinuxKPI: allocate current before taking shrinkers lock ... This fixes following warnings when shrinkers are invoked first time: uma_zalloc_debug: zone "lkpicurr" with the following non-sleepable locks held: exclusive sleep mutex lkpi-shrinker (lkpi-shrinker) uma_zalloc_debug: zone "lkpimm" with the following non-sleepable locks held: exclusive sleep mutex lkpi-shrinker (lkpi-shrinker) Reviewed by: hselasky, manu MFC after: 2 weeks Differential revision: https://reviews.freebsd.org/D32066	2021-09-29 23:12:58 +03:00
Mark Johnston	4af9323542	linuxkpi: Fix the shrinker scan target ... Use the number of items scanned to control the duration of the shrink loop. Otherwise, if a consumer like TTM is not able to free the number of items requested for some reason, the shrinker keeps looping forever. Reviewed by: manu Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D28224	2021-01-18 17:07:55 -05:00
Emmanuel Vadot	2c95fb753f	linuxkpi: Add shrinker support ... A driver can register a shrinker that will be called when the kernel wants to free some memory. Add support for that in linuxkpi and call the registered shrinkers when the lowmem event is triggered. Reviewed by: bz Differential Revision: https://reviews.freebsd.org/D27728	2021-01-12 12:31:00 +01:00