Lines Matching refs:memory

7 Kmemleak provides a way of detecting possible kernel memory leaks in a
12 Valgrind tool (memcheck --leak-check) to detect the memory leaks in
20 thread scans the memory every 10 minutes (by default) and prints the
22 the possible memory leaks:
27 To trigger an intermediate memory scan:
31 To clear the list of all current possible memory leaks:
48   scan=on	- start the automatic memory scanning thread (default)
49   scan=off	- stop the automatic memory scanning thread
50   scan=<secs>	- set the automatic memory scanning period in seconds
52   scan		- trigger a memory scan
53   clear		- clear list of current memory leak suspects, done by
72 The memory allocations via kmalloc, vmalloc, kmem_cache_alloc and
78 An allocated block of memory is considered orphan if no pointer to its
80 scanning the memory (including saved registers). This means that there
83 memory leak.
89   2. scan the memory starting with the data section and stacks, checking
99 Some allocated memory blocks have pointers stored in the kernel's
129 To allow access to previously found memory leaks after kmemleak has been
132 a large part of physical memory.
134 In this situation, you may reclaim memory with:
144 kmemleak_alloc		 - notify of a memory block allocation
145 kmemleak_alloc_percpu	 - notify of a percpu memory block allocation
146 kmemleak_free		 - notify of a memory block freeing
147 kmemleak_free_part	 - notify of a partial memory block freeing
148 kmemleak_free_percpu	 - notify of a percpu memory block freeing
152 kmemleak_scan_area	 - add scan areas inside a memory block
153 kmemleak_no_scan	 - do not scan a memory block
161 The false negatives are real memory leaks (orphan objects) but not
162 reported by kmemleak because values found during the memory scanning
168 The false positives are objects wrongly reported as being memory leaks
171 the memory block is known not to contain other pointers and it will no
177 the minimum age of an object to be reported as a memory leak.
182 The main drawback is the reduced performance of memory allocation and
183 freeing. To avoid other penalties, the memory scanning is only performed
190 number of false negatives. However, it is likely that a real memory leak