File: cma_debugfs.rst

package info (click to toggle)
linux 6.12.57-1
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 1,676,308 kB
  • sloc: ansic: 25,926,848; asm: 269,617; sh: 136,597; python: 65,447; makefile: 55,731; perl: 37,752; xml: 19,284; cpp: 5,895; yacc: 4,927; lex: 2,939; awk: 1,594; sed: 28; ruby: 25
file content (25 lines) | stat: -rw-r--r-- 882 bytes parent folder | download | duplicates (16)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
=====================
CMA Debugfs Interface
=====================

The CMA debugfs interface is useful to retrieve basic information out of the
different CMA areas and to test allocation/release in each of the areas.

Each CMA area represents a directory under <debugfs>/cma/, represented by
its CMA name like below:

	<debugfs>/cma/<cma_name>

The structure of the files created under that directory is as follows:

 - [RO] base_pfn: The base PFN (Page Frame Number) of the zone.
 - [RO] count: Amount of memory in the CMA area.
 - [RO] order_per_bit: Order of pages represented by one bit.
 - [RO] bitmap: The bitmap of page states in the zone.
 - [WO] alloc: Allocate N pages from that CMA area. For example::

	echo 5 > <debugfs>/cma/<cma_name>/alloc

would try to allocate 5 pages from the 'cma_name' area.

 - [WO] free: Free N pages from that CMA area, similar to the above.