Messages in this thread | | | Subject | Re: [PATCH v4] kmemleak: survive in a low-memory situation | From | Qian Cai <> | Date | Thu, 28 Mar 2019 11:24:47 -0400 |
| |
On Thu, 2019-03-28 at 14:59 +0000, Catalin Marinas wrote: 2 > +/* minimum memory pool sizes */ > +#define MIN_OBJECT_POOL (NR_CPUS * 4) > +#define MIN_SCAN_AREA_POOL (NR_CPUS * 1)
I am thinking about making those are tunable, so people could have a big pool depends on their workloads.
Also, I would like to see a way to refill this emergency pool. For example, once OOM kiler freed up more memory. Maybe at the time of kmemleak_scan kthread kicked in and then monitor and refill the pool whenever possible.
| |