perf-kmem.txt 1.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677
  1. perf-kmem(1)
  2. ============
  3. NAME
  4. ----
  5. perf-kmem - Tool to trace/measure kernel memory properties
  6. SYNOPSIS
  7. --------
  8. [verse]
  9. 'perf kmem' {record|stat} [<options>]
  10. DESCRIPTION
  11. -----------
  12. There are two variants of perf kmem:
  13. 'perf kmem record <command>' to record the kmem events
  14. of an arbitrary workload.
  15. 'perf kmem stat' to report kernel memory statistics.
  16. OPTIONS
  17. -------
  18. -i <file>::
  19. --input=<file>::
  20. Select the input file (default: perf.data unless stdin is a fifo)
  21. -f::
  22. --force::
  23. Don't do ownership validation
  24. -v::
  25. --verbose::
  26. Be more verbose. (show symbol address, etc)
  27. --caller::
  28. Show per-callsite statistics
  29. --alloc::
  30. Show per-allocation statistics
  31. -s <key[,key2...]>::
  32. --sort=<key[,key2...]>::
  33. Sort the output (default: 'frag,hit,bytes' for slab and 'bytes,hit'
  34. for page). Available sort keys are 'ptr, callsite, bytes, hit,
  35. pingpong, frag' for slab and 'page, callsite, bytes, hit, order,
  36. migtype, gfp' for page. This option should be preceded by one of the
  37. mode selection options - i.e. --slab, --page, --alloc and/or --caller.
  38. -l <num>::
  39. --line=<num>::
  40. Print n lines only
  41. --raw-ip::
  42. Print raw ip instead of symbol
  43. --slab::
  44. Analyze SLAB allocator events.
  45. --page::
  46. Analyze page allocator events
  47. --live::
  48. Show live page stat. The perf kmem shows total allocation stat by
  49. default, but this option shows live (currently allocated) pages
  50. instead. (This option works with --page option only)
  51. --time=<start>,<stop>::
  52. Only analyze samples within given time window: <start>,<stop>. Times
  53. have the format seconds.microseconds. If start is not given (i.e., time
  54. string is ',x.y') then analysis starts at the beginning of the file. If
  55. stop time is not given (i.e, time string is 'x.y,') then analysis goes
  56. to end of file.
  57. SEE ALSO
  58. --------
  59. linkperf:perf-record[1]