diff options
| author | riastradh <riastradh@NetBSD.org> | 2022-05-30 20:28:30 +0000 |
|---|---|---|
| committer | riastradh <riastradh@NetBSD.org> | 2022-05-30 20:28:30 +0000 |
| commit | 4c3f77befa275218ca55b77528a301466f072cb3 (patch) | |
| tree | 15884fde5f9dad212272351d48ba3f74d8bc7583 /sys/dev/microcode/run/microcode.h | |
| parent | bc9a3d53307310f8239cb82872e068b82d9808a3 (diff) | |
kmem(9): Create dtrace sdt probes for each kmem cache size.
The names of the probes correspond to the names shown in vmstat -m.
This should make it much easier to track down who's allocating memory
when there's a leak, e.g. by getting a histogram of stack traces for
the matching kmem cache pool:
# vmstat -m
Memory resource pool statistics
Name Size Requests Fail Releases Pgreq Pgrel Npage Hiwat Minpg Maxpg Idle
...
kmem-00128 256 62242 0 0 3891 0 3891 3891 0 inf 0
...
# dtrace -n 'sdt:kmem:*:kmem-00128 { @[probefunc, stack()] = count() }'
^C
When there's no leak, the allocs and frees (probefunc) will be roughly
matched; when there's a leak, the allocs will far outnumber the frees.
Diffstat (limited to 'sys/dev/microcode/run/microcode.h')
0 files changed, 0 insertions, 0 deletions
