summaryrefslogtreecommitdiffstats
path: root/gnu/llvm/compiler-rt/lib/sanitizer_common/scripts/cpplint.py
diff options
context:
space:
mode:
authordlg <dlg@openbsd.org>2020-08-10 01:13:28 +0000
committerdlg <dlg@openbsd.org>2020-08-10 01:13:28 +0000
commit59ead937f0e1e45dc43e4cc30e515aaa634b7527 (patch)
treefb7cef3d6cc05299e0e8fe2ecb9e2829a247894a /gnu/llvm/compiler-rt/lib/sanitizer_common/scripts/cpplint.py
parenthardclock(9): fix race with setitimer(2) for ITIMER_VIRTUAL, ITIMER_PROF (diff)
downloadwireguard-openbsd-59ead937f0e1e45dc43e4cc30e515aaa634b7527.tar.xz
wireguard-openbsd-59ead937f0e1e45dc43e4cc30e515aaa634b7527.zip
add the ability to filter which kstats are displayed.
kstats are identified by a "provider:instance:name:unit" tuple, where provider and name are strings, and instance and unit are integers. you can pass tuples as arguments to kstat to select them for display, eg, to see the rxq and txq stats for the first rings on an em0 interface, you can run `kstat em0:0:rxq:0 em0:0:txq:0`. this can be pretty tedious if you want to select a group of stats quickly though, so there's some wildcard and pattern matching support. firstly, empty fields in the tuple are wildcarded, eg, if you want to see all the stats that an mcx0 interface provides then run `kstat mcx0:::`. secondly, strings in a tuple (ie, the provider and name fields) are compared using fnmatch(3) so you can use shell like patterns to match fields. to expand the last example to all mcx interfaces, you can run `kstat mcx*:::`. lastly, you can pass a bare name to match on all kstats with that name. eg, to see the txq stats for all interfaces, just run `kstat txq`.
Diffstat (limited to 'gnu/llvm/compiler-rt/lib/sanitizer_common/scripts/cpplint.py')
0 files changed, 0 insertions, 0 deletions