^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) ------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) ****** perf by examples ******
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4) ------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) [ From an e-mail by Ingo Molnar, http://lkml.org/lkml/2009/8/4/346 ]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) First, discovery/enumeration of available counters can be done via
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) 'perf list':
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) titan:~> perf list
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) [...]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) kmem:kmalloc [Tracepoint event]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) kmem:kmem_cache_alloc [Tracepoint event]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) kmem:kmalloc_node [Tracepoint event]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) kmem:kmem_cache_alloc_node [Tracepoint event]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) kmem:kfree [Tracepoint event]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) kmem:kmem_cache_free [Tracepoint event]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) kmem:mm_page_free [Tracepoint event]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) kmem:mm_page_free_batched [Tracepoint event]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) kmem:mm_page_alloc [Tracepoint event]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) kmem:mm_page_alloc_zone_locked [Tracepoint event]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) kmem:mm_page_pcpu_drain [Tracepoint event]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) kmem:mm_page_alloc_extfrag [Tracepoint event]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) Then any (or all) of the above event sources can be activated and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) measured. For example the page alloc/free properties of a 'hackbench
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) run' are:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) titan:~> perf stat -e kmem:mm_page_pcpu_drain -e kmem:mm_page_alloc
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) -e kmem:mm_page_free_batched -e kmem:mm_page_free ./hackbench 10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) Time: 0.575
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) Performance counter stats for './hackbench 10':
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) 13857 kmem:mm_page_pcpu_drain
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) 27576 kmem:mm_page_alloc
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) 6025 kmem:mm_page_free_batched
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) 20934 kmem:mm_page_free
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) 0.613972165 seconds time elapsed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) You can observe the statistical properties as well, by using the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) 'repeat the workload N times' feature of perf stat:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47) titan:~> perf stat --repeat 5 -e kmem:mm_page_pcpu_drain -e
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) kmem:mm_page_alloc -e kmem:mm_page_free_batched -e
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49) kmem:mm_page_free ./hackbench 10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) Time: 0.627
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) Time: 0.644
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52) Time: 0.564
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53) Time: 0.559
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) Time: 0.626
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) Performance counter stats for './hackbench 10' (5 runs):
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) 12920 kmem:mm_page_pcpu_drain ( +- 3.359% )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) 25035 kmem:mm_page_alloc ( +- 3.783% )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) 6104 kmem:mm_page_free_batched ( +- 0.934% )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) 18376 kmem:mm_page_free ( +- 4.941% )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63) 0.643954516 seconds time elapsed ( +- 2.363% )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) Furthermore, these tracepoints can be used to sample the workload as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66) well. For example the page allocations done by a 'git gc' can be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67) captured the following way:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) titan:~/git> perf record -e kmem:mm_page_alloc -c 1 ./git gc
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70) Counting objects: 1148, done.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71) Delta compression using up to 2 threads.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) Compressing objects: 100% (450/450), done.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) Writing objects: 100% (1148/1148), done.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74) Total 1148 (delta 690), reused 1148 (delta 690)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) [ perf record: Captured and wrote 0.267 MB perf.data (~11679 samples) ]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77) To check which functions generated page allocations:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79) titan:~/git> perf report
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80) # Samples: 10646
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) # Overhead Command Shared Object
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) # ........ ............... ..........................
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85) 23.57% git-repack /lib64/libc-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) 21.81% git /lib64/libc-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87) 14.59% git ./git
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) 11.79% git-repack ./git
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89) 7.12% git /lib64/ld-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90) 3.16% git-repack /lib64/libpthread-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91) 2.09% git-repack /bin/bash
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92) 1.97% rm /lib64/libc-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93) 1.39% mv /lib64/ld-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94) 1.37% mv /lib64/libc-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95) 1.12% git-repack /lib64/ld-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96) 0.95% rm /lib64/ld-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97) 0.90% git-update-serv /lib64/libc-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) 0.73% git-update-serv /lib64/ld-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99) 0.68% perf /lib64/libpthread-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) 0.64% git-repack /usr/lib64/libz.so.1.2.3
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) Or to see it on a more finegrained level:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) titan:~/git> perf report --sort comm,dso,symbol
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) # Samples: 10646
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) # Overhead Command Shared Object Symbol
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) # ........ ............... .......................... ......
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) 9.35% git-repack ./git [.] insert_obj_hash
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) 9.12% git ./git [.] insert_obj_hash
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) 7.31% git /lib64/libc-2.5.so [.] memcpy
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) 6.34% git-repack /lib64/libc-2.5.so [.] _int_malloc
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) 6.24% git-repack /lib64/libc-2.5.so [.] memcpy
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) 5.82% git-repack /lib64/libc-2.5.so [.] __GI___fork
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) 5.47% git /lib64/libc-2.5.so [.] _int_malloc
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) 2.99% git /lib64/libc-2.5.so [.] memset
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) Furthermore, call-graph sampling can be done too, of page
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) allocations - to see precisely what kind of page allocations there
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) are:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) titan:~/git> perf record -g -e kmem:mm_page_alloc -c 1 ./git gc
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) Counting objects: 1148, done.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) Delta compression using up to 2 threads.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) Compressing objects: 100% (450/450), done.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) Writing objects: 100% (1148/1148), done.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) Total 1148 (delta 690), reused 1148 (delta 690)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) [ perf record: Captured and wrote 0.963 MB perf.data (~42069 samples) ]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131) titan:~/git> perf report -g
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) # Samples: 10686
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) # Overhead Command Shared Object
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) # ........ ............... ..........................
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) 23.25% git-repack /lib64/libc-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139) |--50.00%-- _int_free
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) |--37.50%-- __GI___fork
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) | make_child
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144) |--12.50%-- ptmalloc_unlock_all2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) | make_child
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) --6.25%-- __GI_strcpy
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) 21.61% git /lib64/libc-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) |--30.00%-- __GI_read
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151) | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) | --83.33%-- git_config_from_file
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) | git_config
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) [...]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) Or you can observe the whole system's page allocations for 10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) seconds:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) titan:~/git> perf stat -a -e kmem:mm_page_pcpu_drain -e
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) kmem:mm_page_alloc -e kmem:mm_page_free_batched -e
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) kmem:mm_page_free sleep 10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) Performance counter stats for 'sleep 10':
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) 171585 kmem:mm_page_pcpu_drain
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) 322114 kmem:mm_page_alloc
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) 73623 kmem:mm_page_free_batched
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) 254115 kmem:mm_page_free
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) 10.000591410 seconds time elapsed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) Or observe how fluctuating the page allocations are, via statistical
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174) analysis done over ten 1-second intervals:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) titan:~/git> perf stat --repeat 10 -a -e kmem:mm_page_pcpu_drain -e
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) kmem:mm_page_alloc -e kmem:mm_page_free_batched -e
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) kmem:mm_page_free sleep 1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) Performance counter stats for 'sleep 1' (10 runs):
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) 17254 kmem:mm_page_pcpu_drain ( +- 3.709% )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) 34394 kmem:mm_page_alloc ( +- 4.617% )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) 7509 kmem:mm_page_free_batched ( +- 4.820% )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) 25653 kmem:mm_page_free ( +- 3.672% )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) 1.058135029 seconds time elapsed ( +- 3.089% )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189) Or you can annotate the recorded 'git gc' run on a per symbol basis
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) and check which instructions/source-code generated page allocations:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) titan:~/git> perf annotate __GI___fork
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) ------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) Percent | Source code & Disassembly of libc-2.5.so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195) ------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) :
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) :
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) : Disassembly of section .plt:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199) : Disassembly of section .text:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200) :
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) : 00000031a2e95560 <__fork>:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202) [...]
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) 0.00 : 31a2e95602: b8 38 00 00 00 mov $0x38,%eax
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) 0.00 : 31a2e95607: 0f 05 syscall
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205) 83.42 : 31a2e95609: 48 3d 00 f0 ff ff cmp $0xfffffffffffff000,%rax
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) 0.00 : 31a2e9560f: 0f 87 4d 01 00 00 ja 31a2e95762 <__fork+0x202>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) 0.00 : 31a2e95615: 85 c0 test %eax,%eax
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) ( this shows that 83.42% of __GI___fork's page allocations come from
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) the 0x38 system call it performs. )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) etc. etc. - a lot more is possible. I could list a dozen of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) other different usecases straight away - neither of which is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) possible via /proc/vmstat.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) /proc/vmstat is not in the same league really, in terms of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) expressive power of system analysis and performance
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) analysis.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) All that the above results needed were those new tracepoints
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) in include/tracing/events/kmem.h.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) Ingo
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225)
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags