€•w[      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ+/translations/zh_CN/mm/allocation-profiling”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/zh_TW/mm/allocation-profiling”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/it_IT/mm/allocation-profiling”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/ja_JP/mm/allocation-profiling”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/ko_KR/mm/allocation-profiling”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/pt_BR/mm/allocation-profiling”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/sp_SP/mm/allocation-profiling”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh·sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1hµhhh²hh³ŒE/var/lib/git/docbuild/linux/Documentation/mm/allocation-profiling.rst”h´KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒMEMORY ALLOCATION PROFILING”h]”hŒMEMORY ALLOCATION PROFILING”…””}”(hhÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhhÊh²hh³hÇh´KubhŒ	paragraph”“”)”}”(hŒmLow overhead (suitable for production) accounting of all memory allocations,
tracked by file and line number.”h]”hŒmLow overhead (suitable for production) accounting of all memory allocations,
tracked by file and line number.”…””}”(hhßh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhhÊh²hubhÞ)”}”(hŒ4Usage:
kconfig options:
- CONFIG_MEM_ALLOC_PROFILING”h]”hŒ4Usage:
kconfig options:
- CONFIG_MEM_ALLOC_PROFILING”…””}”(hhíh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K
hhÊh²hubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒ.CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT
”h]”hÞ)”}”(hŒ-CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT”h]”hŒ-CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j   hhýh²hh³hÇh´Nubj  )”}”(hŒvCONFIG_MEM_ALLOC_PROFILING_DEBUG
adds warnings for allocations that weren't accounted because of a
missing annotation
”h]”hÞ)”}”(hŒuCONFIG_MEM_ALLOC_PROFILING_DEBUG
adds warnings for allocations that weren't accounted because of a
missing annotation”h]”hŒwCONFIG_MEM_ALLOC_PROFILING_DEBUG
adds warnings for allocations that werenâ€™t accounted because of a
missing annotation”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j   hhýh²hh³hÇh´Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1hûh³hÇh´KhhÊh²hubhŒdefinition_list”“”)”}”(hhh]”(hŒdefinition_list_item”“”)”}”(hX©  Boot parameter:
sysctl.vm.mem_profiling={0|1|never}[,compressed]

When set to "never", memory allocation profiling overhead is minimized and it
cannot be enabled at runtime (sysctl becomes read-only).
When CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=y, default value is "1".
When CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=n, default value is "never".
"compressed" optional parameter will try to store page tag references in a
compact format, avoiding page extensions. This results in improved performance
and memory consumption, however it might fail depending on system configuration.
If compression fails, a warning is issued and memory allocation profiling gets
disabled.
”h]”(hŒterm”“”)”}”(hŒBoot parameter:”h]”hŒBoot parameter:”…””}”(hjG  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jE  h³hÇh´KhjA  ubhŒ
definition”“”)”}”(hhh]”(hÞ)”}”(hŒ0sysctl.vm.mem_profiling={0|1|never}[,compressed]”h]”hŒ0sysctl.vm.mem_profiling={0|1|never}[,compressed]”…””}”(hjZ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhjW  ubhÞ)”}”(hXf  When set to "never", memory allocation profiling overhead is minimized and it
cannot be enabled at runtime (sysctl becomes read-only).
When CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=y, default value is "1".
When CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=n, default value is "never".
"compressed" optional parameter will try to store page tag references in a
compact format, avoiding page extensions. This results in improved performance
and memory consumption, however it might fail depending on system configuration.
If compression fails, a warning is issued and memory allocation profiling gets
disabled.”h]”hXv  When set to â€œneverâ€, memory allocation profiling overhead is minimized and it
cannot be enabled at runtime (sysctl becomes read-only).
When CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=y, default value is â€œ1â€.
When CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=n, default value is â€œneverâ€.
â€œcompressedâ€ optional parameter will try to store page tag references in a
compact format, avoiding page extensions. This results in improved performance
and memory consumption, however it might fail depending on system configuration.
If compression fails, a warning is issued and memory allocation profiling gets
disabled.”…””}”(hjh  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhjW  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jU  hjA  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j?  h³hÇh´Khj<  ubj@  )”}”(hXØ  sysctl:
/proc/sys/vm/mem_profiling

1: Enable memory profiling.

0: Disable memory profiling.

The default value depends on CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT.

When CONFIG_MEM_ALLOC_PROFILING_DEBUG=y, this control is read-only to avoid
warnings produced by allocations made while profiling is disabled and freed
when it's enabled.

/proc/sys/vm/mem_profiling_compressed

1: Page alloc tag compression is enabled.

0: Page alloc tag compression is disabled.

This reflects a static boot-time configuration of how page allocation tags are
stored (in page flags when compression is enabled and in page_ext when disabled).
Toggling ``mem_profiling`` at runtime does not change the state of
``mem_profiling_compressed``.
”h]”(jF  )”}”(hŒsysctl:”h]”hŒsysctl:”…””}”(hj†  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jE  h³hÇh´K7hj‚  ubjV  )”}”(hhh]”(hÞ)”}”(hŒ/proc/sys/vm/mem_profiling”h]”hŒ/proc/sys/vm/mem_profiling”…””}”(hj—  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K"hj”  ubhÞ)”}”(hŒ1: Enable memory profiling.”h]”hŒ1: Enable memory profiling.”…””}”(hj¥  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K$hj”  ubhÞ)”}”(hŒ0: Disable memory profiling.”h]”hŒ0: Disable memory profiling.”…””}”(hj³  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K&hj”  ubhÞ)”}”(hŒKThe default value depends on CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT.”h]”hŒKThe default value depends on CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT.”…””}”(hjÁ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K(hj”  ubhÞ)”}”(hŒªWhen CONFIG_MEM_ALLOC_PROFILING_DEBUG=y, this control is read-only to avoid
warnings produced by allocations made while profiling is disabled and freed
when it's enabled.”h]”hŒ¬When CONFIG_MEM_ALLOC_PROFILING_DEBUG=y, this control is read-only to avoid
warnings produced by allocations made while profiling is disabled and freed
when itâ€™s enabled.”…””}”(hjÏ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K*hj”  ubhÞ)”}”(hŒ%/proc/sys/vm/mem_profiling_compressed”h]”hŒ%/proc/sys/vm/mem_profiling_compressed”…””}”(hjÝ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K.hj”  ubhÞ)”}”(hŒ)1: Page alloc tag compression is enabled.”h]”hŒ)1: Page alloc tag compression is enabled.”…””}”(hjë  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K0hj”  ubhÞ)”}”(hŒ*0: Page alloc tag compression is disabled.”h]”hŒ*0: Page alloc tag compression is disabled.”…””}”(hjù  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K2hj”  ubhÞ)”}”(hX  This reflects a static boot-time configuration of how page allocation tags are
stored (in page flags when compression is enabled and in page_ext when disabled).
Toggling ``mem_profiling`` at runtime does not change the state of
``mem_profiling_compressed``.”h]”(hŒªThis reflects a static boot-time configuration of how page allocation tags are
stored (in page flags when compression is enabled and in page_ext when disabled).
Toggling ”…””}”(hj  h²hh³Nh´NubhŒliteral”“”)”}”(hŒ``mem_profiling``”h]”hŒmem_profiling”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubhŒ) at runtime does not change the state of
”…””}”(hj  h²hh³Nh´Nubj  )”}”(hŒ``mem_profiling_compressed``”h]”hŒmem_profiling_compressed”…””}”(hj#  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubhŒ.”…””}”(hj  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K4hj”  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jU  hj‚  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j?  h³hÇh´K7hj<  h²hubj@  )”}”(hXi  Runtime info:
/proc/allocinfo

Profiling data can be retrieved either by reading `/proc/allocinfo` directly as
text or programmatically via `ioctl()` calls defined in `<uapi/linux/alloc_tag.h>`.
The ioctl interface supports structured binary data extraction as well as filtering
by module name, function, file, line number, accuracy, or allocation size limits.
”h]”(jF  )”}”(hŒRuntime info:”h]”hŒRuntime info:”…””}”(hjK  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jE  h³hÇh´K?hjG  ubjV  )”}”(hhh]”(hÞ)”}”(hŒ/proc/allocinfo”h]”hŒ/proc/allocinfo”…””}”(hj\  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K:hjY  ubhÞ)”}”(hXI  Profiling data can be retrieved either by reading `/proc/allocinfo` directly as
text or programmatically via `ioctl()` calls defined in `<uapi/linux/alloc_tag.h>`.
The ioctl interface supports structured binary data extraction as well as filtering
by module name, function, file, line number, accuracy, or allocation size limits.”h]”(hŒ2Profiling data can be retrieved either by reading ”…””}”(hjj  h²hh³Nh´NubhŒtitle_reference”“”)”}”(hŒ`/proc/allocinfo`”h]”hŒ/proc/allocinfo”…””}”(hjt  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jr  hjj  ubhŒ* directly as
text or programmatically via ”…””}”(hjj  h²hh³Nh´Nubjs  )”}”(hŒ	`ioctl()`”h]”hŒioctl()”…””}”(hj†  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jr  hjj  ubhŒ calls defined in ”…””}”(hjj  h²hh³Nh´Nubjs  )”}”(hŒ`<uapi/linux/alloc_tag.h>`”h]”hŒ<uapi/linux/alloc_tag.h>”…””}”(hj˜  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jr  hjj  ubhŒ§.
The ioctl interface supports structured binary data extraction as well as filtering
by module name, function, file, line number, accuracy, or allocation size limits.”…””}”(hjj  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K<hjY  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jU  hjG  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j?  h³hÇh´K?hj<  h²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1j:  hhÊh²hh³hÇh´NubhÞ)”}”(hŒExample output::”h]”hŒExample output:”…””}”(hjÂ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KAhhÊh²hubhŒliteral_block”“”)”}”(hX  root@moria-kvm:~# sort -g /proc/allocinfo|tail|numfmt --to=iec
      2.8M    22648 fs/kernfs/dir.c:615 func:__kernfs_new_node
      3.8M      953 mm/memory.c:4214 func:alloc_anon_folio
      4.0M     1010 drivers/staging/ctagmod/ctagmod.c:20 [ctagmod] func:ctagmod_start
      4.1M        4 net/netfilter/nf_conntrack_core.c:2567 func:nf_ct_alloc_hashtable
      6.0M     1532 mm/filemap.c:1919 func:__filemap_get_folio
      8.8M     2785 kernel/fork.c:307 func:alloc_thread_stack_node
       13M      234 block/blk-mq.c:3421 func:blk_mq_alloc_rqs
       14M     3520 mm/mm_init.c:2530 func:alloc_large_system_hash
       15M     3656 mm/readahead.c:247 func:page_cache_ra_unbounded
       55M     4887 mm/slub.c:2259 func:alloc_slab_page
      122M    31168 mm/page_ext.c:270 func:alloc_page_ext”h]”hX  root@moria-kvm:~# sort -g /proc/allocinfo|tail|numfmt --to=iec
      2.8M    22648 fs/kernfs/dir.c:615 func:__kernfs_new_node
      3.8M      953 mm/memory.c:4214 func:alloc_anon_folio
      4.0M     1010 drivers/staging/ctagmod/ctagmod.c:20 [ctagmod] func:ctagmod_start
      4.1M        4 net/netfilter/nf_conntrack_core.c:2567 func:nf_ct_alloc_hashtable
      6.0M     1532 mm/filemap.c:1919 func:__filemap_get_folio
      8.8M     2785 kernel/fork.c:307 func:alloc_thread_stack_node
       13M      234 block/blk-mq.c:3421 func:blk_mq_alloc_rqs
       14M     3520 mm/mm_init.c:2530 func:alloc_large_system_hash
       15M     3656 mm/readahead.c:247 func:page_cache_ra_unbounded
       55M     4887 mm/slub.c:2259 func:alloc_slab_page
      122M    31168 mm/page_ext.c:270 func:alloc_page_ext”…””}”hjÒ  sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1jÐ  h³hÇh´KChhÊh²hubhÉ)”}”(hhh]”(hÎ)”}”(hŒTheory of operation”h]”hŒTheory of operation”…””}”(hjã  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjà  h²hh³hÇh´KQubhÞ)”}”(hX'  Memory allocation profiling builds off of code tagging, which is a library for
declaring static structs (that typically describe a file and line number in
some way, hence code tagging) and then finding and operating on them at runtime,
- i.e. iterating over them to print them in debugfs/procfs.”h]”hX'  Memory allocation profiling builds off of code tagging, which is a library for
declaring static structs (that typically describe a file and line number in
some way, hence code tagging) and then finding and operating on them at runtime,
- i.e. iterating over them to print them in debugfs/procfs.”…””}”(hjñ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KShjà  h²hubhÞ)”}”(hX  To add accounting for an allocation call, we replace it with a macro
invocation, alloc_hooks(), that
- declares a code tag
- stashes a pointer to it in task_struct
- calls the real allocation function
- and finally, restores the task_struct alloc tag pointer to its previous value.”h]”hX  To add accounting for an allocation call, we replace it with a macro
invocation, alloc_hooks(), that
- declares a code tag
- stashes a pointer to it in task_struct
- calls the real allocation function
- and finally, restores the task_struct alloc tag pointer to its previous value.”…””}”(hjÿ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KXhjà  h²hubhÞ)”}”(hXX  This allows for alloc_hooks() calls to be nested, with the most recent one
taking effect. This is important for allocations internal to the mm/ code that
do not properly belong to the outer allocation context and should be counted
separately: for example, slab object extension vectors, or when the slab
allocates pages from the page allocator.”h]”hXX  This allows for alloc_hooks() calls to be nested, with the most recent one
taking effect. This is important for allocations internal to the mm/ code that
do not properly belong to the outer allocation context and should be counted
separately: for example, slab object extension vectors, or when the slab
allocates pages from the page allocator.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K_hjà  h²hubhÞ)”}”(hXV  Thus, proper usage requires determining which function in an allocation call
stack should be tagged. There are many helper functions that essentially wrap
e.g. kmalloc() and do a little more work, then are called in multiple places;
we'll generally want the accounting to happen in the callers of these helpers,
not in the helpers themselves.”h]”hXX  Thus, proper usage requires determining which function in an allocation call
stack should be tagged. There are many helper functions that essentially wrap
e.g. kmalloc() and do a little more work, then are called in multiple places;
weâ€™ll generally want the accounting to happen in the callers of these helpers,
not in the helpers themselves.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kehjà  h²hubhÞ)”}”(hŒ‹To fix up a given helper, for example foo(), do the following:
- switch its allocation call to the _noprof() version, e.g. kmalloc_noprof()”h]”hŒ‹To fix up a given helper, for example foo(), do the following:
- switch its allocation call to the _noprof() version, e.g. kmalloc_noprof()”…””}”(hj)  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kkhjà  h²hubhü)”}”(hhh]”(j  )”}”(hŒrename it to foo_noprof()
”h]”hÞ)”}”(hŒrename it to foo_noprof()”h]”hŒrename it to foo_noprof()”…””}”(hj>  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Knhj:  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j   hj7  h²hh³hÇh´Nubj  )”}”(hŒ`define a macro version of foo() like so:

#define foo(...) alloc_hooks(foo_noprof(__VA_ARGS__))
”h]”(hÞ)”}”(hŒ(define a macro version of foo() like so:”h]”hŒ(define a macro version of foo() like so:”…””}”(hjV  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KphjR  ubhÞ)”}”(hŒ5#define foo(...) alloc_hooks(foo_noprof(__VA_ARGS__))”h]”hŒ5#define foo(...) alloc_hooks(foo_noprof(__VA_ARGS__))”…””}”(hjd  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KrhjR  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j   hj7  h²hh³hÇh´Nubeh}”(h]”h ]”h"]”h$]”h&]”j8  j9  uh1hûh³hÇh´Knhjà  h²hubhÞ)”}”(hŒRIt's also possible to stash a pointer to an alloc tag in your own data structures.”h]”hŒTItâ€™s also possible to stash a pointer to an alloc tag in your own data structures.”…””}”(hj~  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kthjà  h²hubhÞ)”}”(hX  Do this when you're implementing a generic data structure that does allocations
"on behalf of" some other code - for example, the rhashtable code. This way,
instead of seeing a large line in /proc/allocinfo for rhashtable.c, we can
break it out by rhashtable type.”h]”hX  Do this when youâ€™re implementing a generic data structure that does allocations
â€œon behalf ofâ€ some other code - for example, the rhashtable code. This way,
instead of seeing a large line in /proc/allocinfo for rhashtable.c, we can
break it out by rhashtable type.”…””}”(hjŒ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kvhjà  h²hubhÞ)”}”(hŒYTo do so:
- Hook your data structure's init function, like any other allocation function.”h]”hŒ[To do so:
- Hook your data structureâ€™s init function, like any other allocation function.”…””}”(hjš  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K{hjà  h²hubhü)”}”(hhh]”(j  )”}”(hŒtWithin your init function, use the convenience macro alloc_tag_record() to
record alloc tag in your data structure.
”h]”hÞ)”}”(hŒsWithin your init function, use the convenience macro alloc_tag_record() to
record alloc tag in your data structure.”h]”hŒsWithin your init function, use the convenience macro alloc_tag_record() to
record alloc tag in your data structure.”…””}”(hj¯  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K~hj«  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j   hj¨  h²hh³hÇh´Nubj  )”}”(hŒlThen, use the following form for your allocations:
alloc_hooks_tag(ht->your_saved_tag, kmalloc_noprof(...))
”h]”hÞ)”}”(hŒkThen, use the following form for your allocations:
alloc_hooks_tag(ht->your_saved_tag, kmalloc_noprof(...))”h]”hŒkThen, use the following form for your allocations:
alloc_hooks_tag(ht->your_saved_tag, kmalloc_noprof(...))”…””}”(hjÇ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhjÃ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j   hj¨  h²hh³hÇh´Nubeh}”(h]”h ]”h"]”h$]”h&]”j8  j9  uh1hûh³hÇh´K~hjà  h²hubeh}”(h]”Œtheory-of-operation”ah ]”h"]”Œtheory of operation”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´KQubhÉ)”}”(hhh]”(hÎ)”}”(hŒNotes”h]”hŒNotes”…””}”(hjì  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjé  h²hh³hÇh´K…ubhü)”}”(hhh]”j  )”}”(hŒ¢When a slab object is allocated from KFENCE, its accounting is skipped.
KFENCE allocations are rare and limited to a small number, so this omission
is negligible.”h]”hÞ)”}”(hŒ¢When a slab object is allocated from KFENCE, its accounting is skipped.
KFENCE allocations are rare and limited to a small number, so this omission
is negligible.”h]”hŒ¢When a slab object is allocated from KFENCE, its accounting is skipped.
KFENCE allocations are rare and limited to a small number, so this omission
is negligible.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K‡hjý  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j   hjú  h²hh³hÇh´Nubah}”(h]”h ]”h"]”h$]”h&]”j8  j9  uh1hûh³hÇh´K‡hjé  h²hubeh}”(h]”Œnotes”ah ]”h"]”Œnotes”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´K…ubeh}”(h]”Œmemory-allocation-profiling”ah ]”h"]”Œmemory allocation profiling”ah$]”h&]”uh1hÈhhh²hh³hÇh´Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”hÇuh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(hÍNŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jN  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”hÇŒ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j(  j%  jæ  jã  j   j  uŒ	nametypes”}”(j(  ‰jæ  ‰j   ‰uh}”(j%  hÊjã  jà  j  jé  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nh²hub.