Searched refs:slabinfo (Results 1 – 8 of 8) sorted by relevance
10 * gcc -o slabinfo slabinfo.c28 struct slabinfo { struct 49 } slabinfo[MAX_SLABS]; variable 54 struct slabinfo *slab;113 printf("slabinfo 4/15/2011. (c) 2007 sgi/(c) 2011 Linux Foundation.\n\n" in usage() 114 "slabinfo [-aABDefhilLnoPrsStTUvXz1] [N=K] [-dafzput] [slab-regexp]\n" in usage() 208 static void set_obj(struct slabinfo *s, const char *name, int n) in set_obj() 222 static unsigned long read_slab_obj(struct slabinfo *s, const char *name) in read_slab_obj() 241 static unsigned long read_debug_slab_obj(struct slabinfo *[all...]
6 BUILD_TARGETS=page-types slabinfo page_owner_sort thp_swap_allocator_test26 $(RM) page-types slabinfo page_owner_sort thp_swap_allocator_test
2 slabinfo
15 Typically one would then use the ``slabinfo`` command to get statistical16 data and perform operation on the slabs. By default ``slabinfo`` only lists17 slabs that have data in them. See "slabinfo -h" for more options when18 running the command. ``slabinfo`` can be compiled with21 gcc -o slabinfo tools/mm/slabinfo.c23 Some of the modes of operation of ``slabinfo`` require that slub debugging126 ``slabinfo -a`` displays which slabs were merged together.132 order to do so you must have the ``slabinfo`` tool. Then you can do135 slabinfo -v140 In that case ``slabinfo -v`` simply tests all reachable objects. Usually[all …]
277 def slabinfo(): function324 slabinfo()
433 struct slabinfo { struct446 void get_slabinfo(struct kmem_cache *s, struct slabinfo *sinfo); argument
9915 void get_slabinfo(struct kmem_cache *s, struct slabinfo *sinfo) in get_slabinfo()
311 entries of /proc/slabinfo325 (see /proc/slabinfo)