Provided by: trace-cmd_2.8.3-4build1_amd64 bug

NAME

       trace-cmd-mem - show memory usage of certain kmem events

SYNOPSIS

       trace-cmd mem [OPTIONS][input-file]

DESCRIPTION

       The trace-cmd(1) mem requires a trace-cmd record that enabled the following events:

           kmalloc
           kmalloc_node
           kfree
           kmem_cache_alloc
           kmem_cache_alloc_node
           kmem_cache_alloc_free

       It then reads the amount requested and the ammount freed as well as the functions that
       called the allocation. It then reports the final amount of bytes requested and allocated,
       along with the total amount allocated and requested, as well as the max allocation and
       requested during the run. It reports the amount of wasted bytes (allocated - requested)
       that was not freed, as well as the max wasted amount during the run. The list is sorted by
       descending order of wasted bytes after the run.

                   Function                Waste   Alloc   req             TotAlloc     TotReq             MaxAlloc     MaxReq     MaxWaste
                   --------                -----   -----   ---             --------     ------             --------     ------     --------
             rb_allocate_cpu_buffer        768     2304    1536                2304       1536                 2304       1536     768
                    alloc_pipe_info        400     1152    752                 1152        752                 1152        752     400
                     instance_mkdir        252     544     292                  544        292                  544        292     252
                          __d_alloc        215     1086560 1086345          1087208    1086993              1086560    1086345     215
                     get_empty_filp        72      2304    2232                4864       4712                 4864       4712     152
                           mm_alloc        40      960     920                  960        920                  960        920     40
                      prepare_creds        32      192     160                 1728       1440                 1728       1440     288
               tracing_buffers_open        8       32      24                    32         24                   32         24     8
                             do_brk        0       0       0                    368        368                  368        368     0
           journal_add_journal_head        0       6048    6048                6048       6048                 6048       6048     0
                      journal_start        0       0       0                   1224       1224                   48         48     0
                __rb_allocate_pages        0       3289856 3289856          3289856    3289856              3289856    3289856     0
                     anon_vma_alloc        0       0       0                    936        936                  864        864     0
                                                                   [...]

OPTIONS

       -i input-file
           By default, trace-cmd hist will read the file trace.dat. But the -i option open up the
           given input-file instead. Note, the input file may also be specified as the last item
           on the command line.

SEE ALSO

       trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-start(1),
       trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(1), trace-cmd-hist(1),
       trace-cmd-split(1), trace-cmd-listen(1)

AUTHOR

       Written by Steven Rostedt, <rostedt@goodmis.org[1]>

RESOURCES

       git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git

COPYING

       Copyright (C) 2013 Red Hat, Inc. Free use of this software is granted under the terms of
       the GNU Public License (GPL).

NOTES

        1. rostedt@goodmis.org
           mailto:rostedt@goodmis.org

                                            03/23/2020                           TRACE-CMD-MEM(1)