| /Documentation/filesystems/ext4/ |
| D | group_descr.rst | 39 number, and the group descriptor structure. Both block and inode bitmap
41 entire bitmap.
56 - Lower 32-bits of location of block bitmap.
60 - Lower 32-bits of location of inode bitmap.
84 - Lower 32-bits of location of snapshot exclusion bitmap.
88 - Lower 16-bits of the block bitmap checksum.
92 - Lower 16-bits of the inode bitmap checksum.
116 - Upper 32-bits of location of block bitmap.
120 - Upper 32-bits of location of inodes bitmap.
144 - Upper 32-bits of location of snapshot exclusion bitmap.
[all …]
|
| D | bitmaps.rst | 6 The data block bitmap tracks the usage of data blocks within the block
9 The inode bitmap records which entries in the inode table are in use.
16 of the kernel and e2fsprogs code pretends that the block bitmap contains
|
| D | blockgroup.rst | 17 - Data Block Bitmap
18 - inode Bitmap
43 copy, the block group begins with the data block bitmap. Note also that
67 logical block group; the bitmap spaces and the inode table space in the
126 therefore the on-disk bitmap blocks are not initialized. This is
|
| D | bigalloc.rst | 16 bitmap addresses a power of two number of blocks. For example, if the
19 This means that each bit in the block allocation bitmap now addresses
|
| /Documentation/virt/kvm/arm/ |
| D | fw-pseudo-registers.rst | 78 Bitmap Feature Firmware Registers
82 hypercall services in the form of a feature-bitmap to the userspace. This
83 bitmap is translated to the services that are available to the guest.
90 desired bitmap back via SET_ONE_REG. The features for the registers that
98 The pseudo-firmware bitmap register are as follows:
101 Controls the bitmap of the ARM Standard Secure Service Calls.
110 Controls the bitmap of the ARM Standard Hypervisor Service Calls.
119 Controls the bitmap of the Vendor specific Hypervisor Service Calls.
135 -EINVAL Invalid bitmap written to the register.
|
| /Documentation/filesystems/ |
| D | qnx6.rst | 54 parts. (Inode, Bitmap and Longfilenames)
153 Bitmap section in Specification
156 The qnx6fs filesystem allocation bitmap is stored in a tree under bitmap
157 root node in the superblock and each bit in the bitmap represents one
164 Bits at the end of the last bitmap block are set to 1, if the device is
165 smaller than addressing space in the bitmap.
167 Bitmap system area
170 The bitmap itself is divided into three parts.
181 blocks represented by the upper half bitmap system area bits.
183 Bitmap blocks, Inode blocks and indirect addressing blocks for those two
|
| /Documentation/admin-guide/mm/ |
| D | idle_page_tracking.rst | 23 ``/sys/kernel/mm/page_idle/bitmap``.
25 The file implements a bitmap where each bit corresponds to a memory page. The
26 bitmap is represented by an array of 8-byte integers, and the page at PFN #i is
35 current bitmap value.
45 Reading from or writing to ``/sys/kernel/mm/page_idle/bitmap`` will return
54 ``/sys/kernel/mm/page_idle/bitmap``. The pages can be found by reading
61 3. Read ``/sys/kernel/mm/page_idle/bitmap`` and count the number of bits set.
99 is set manually, by writing to ``/sys/kernel/mm/page_idle/bitmap`` (see the
117 result noticeably. In order not to stall scanning of the idle page bitmap,
|
| D | cma_debugfs.rst | 18 - [RO] bitmap: The bitmap of page states in the zone.
|
| /Documentation/driver-api/md/ |
| D | md-cluster.rst | 40 2.1 Bitmap lock resource (bm_lockres)
48 subsystem. Since DLM starts node count from one and bitmap slots
50 at the bitmap slot number.
52 The LVB of the bitmap lock for a particular node records the range
121 If a node is stopped locally but the bitmap
220 - acquires the bitmap<number> lock of the failed node
221 - opens the bitmap
222 - reads the bitmap of the failed node
223 - copies the set bitmap to local node
224 - cleans the bitmap of the failed node
[all …]
|
| /Documentation/translations/zh_CN/core-api/ |
| D | kernel-api.rst | 80 lib/bitmap.c
82 include/linux/bitmap.h
84 include/linux/bitmap.h
86 include/linux/bitmap.h
88 lib/bitmap.c
90 lib/bitmap.c
92 include/linux/bitmap.h
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-papr-pmem | 8 more bits set in the dimm-health-bitmap retrieved in
70 (RO) Reports the health bitmap inject bitmap that is applied to
71 bitmap received from PowerVM via the H_SCM_HEALTH. This is used
|
| D | sysfs-driver-intel-m10-bmc-sec-update | 36 signing keys for the static region. The standard bitmap
45 standard bitmap list format is used (e.g. "1,2-6,9").
52 signing keys for the BMC. The standard bitmap list format
|
| /Documentation/core-api/ |
| D | kernel-api.rst | 69 Bitmap Operations
72 .. kernel-doc:: lib/bitmap.c
73 :doc: bitmap introduction
75 .. kernel-doc:: include/linux/bitmap.h
76 :doc: declare bitmap
78 .. kernel-doc:: include/linux/bitmap.h
79 :doc: bitmap overview
81 .. kernel-doc:: include/linux/bitmap.h
82 :doc: bitmap bitops
84 .. kernel-doc:: lib/bitmap.c
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-integrity.rst | 28 There's an alternate mode of operation where dm-integrity uses a bitmap
29 instead of a journal. If a bit in the bitmap is 1, the corresponding
31 crashes, the unsynchronized regions will be recalculated. The bitmap mode
86 B - bitmap mode - data and metadata are written without any
87 synchronization, the driver maintains a bitmap of dirty
177 In the bitmap mode, this parameter specifies the number of
178 512-byte sectors that corresponds to one bitmap bit.
181 The bitmap flush interval in milliseconds. The metadata buffers
254 - journal area contains the bitmap of dirty
|
| /Documentation/virt/kvm/loongarch/ |
| D | hypercalls.rst | 77 - a1: Lower part of the bitmap for destination physical CPUIDs
78 - a2: Higher part of the bitmap for destination physical CPUIDs
79 - a3: The lowest physical CPUID in the bitmap
83 bitmap contained in the first two input registers (a1 and a2).
|
| /Documentation/networking/ |
| D | radiotap-headers.rst | 21 There is a fixed portion at the start which contains a u32 bitmap that defines
30 [ <possible argument bitmap extensions ... > ]
35 indicates that there is another u32 bitmap following (shown as "possible
36 argument bitmap extensions..." above), and the start of the arguments is moved
88 0x04, 0x0c, 0x00, 0x00, // <-- bitmap
|
| D | mac80211-auth-assoc-deauth.txt | 27 mac80211->driver: bss_info_changed(set BSSID, basic rate bitmap)
55 mac80211->driver: bss_info_changed(set BSSID, basic rate bitmap)
|
| /Documentation/admin-guide/ |
| D | md.rst | 350 bitmap/location
351 This indicates where the write-intent bitmap for the array is
362 bitmap/chunksize
368 bitmap/time_base
369 The time, in seconds, between looking for bits in the bitmap to
374 bitmap/backlog
382 bitmap/metadata
386 is the default and means the metadata for the bitmap
391 means that bitmap metadata is managed externally to
394 bitmap/can_clear
[all …]
|
| /Documentation/driver-api/gpio/ |
| D | board.rst | 197 mapped to the device determines if the array qualifies for fast bitmap
198 processing. If yes, a bitmap is passed over get/set array functions directly
201 In order to qualify for fast bitmap processing, the array must meet the
208 Otherwise fast bitmap processing path is not used in order to avoid consecutive
212 If the array applies for fast bitmap processing path, pins which belong to
215 output. Moreover, open drain and open source pins are excluded from fast bitmap
|
| /Documentation/input/devices/ |
| D | alps.rst | 175 given axis. Thus the bitmap packet can be used for low-resolution multi-touch
213 byte 6: bitmap data (described below)
214 byte 7: bitmap data (described below)
216 The last two bytes represent a partial bitmap packet, with 3 full packets
217 required to construct a complete bitmap packet. Once assembled, the 6-byte
218 bitmap packet has the following format::
229 1) In the bitmap data, bit 6 of byte 0 serves as a sync byte to
230 identify the first fragment of a bitmap packet.
232 2) The bitmaps represent the same data as in the v3 bitmap packets, although
239 4) There is a 3 to 1 ratio of position packets to bitmap packets. Therefore
|
| /Documentation/devicetree/bindings/perf/ |
| D | riscv,pmu.yaml | 58 MHPMCOUNTERx in a bitmap format that can be used to monitor these range
66 - description: bitmap of MHPMCOUNTERx for this event
72 and all the MHPMCOUNTERx in a bitmap format that can be used to monitor
90 bitmap of all MHPMCOUNTERx that can monitor the range of events
|
| /Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_osd.rst | 433 - :cspan:`1` 1 bit bitmap
439 - 2 bit bitmap
445 - 4 bit bitmap
451 - 8 bit bitmap
457 - 1 Bit bitmap half resolution
463 - 2 Bit bitmap half resolution
469 - 4 Bit bitmap half resolution
475 - 8 Bit bitmap half resolution
|
| /Documentation/devicetree/bindings/opp/ |
| D | opp-v2-kryo-cpu.yaml | 23 the OPP framework with required information (existing HW bitmap).
56 A single 32 bit bitmap value, representing compatible HW.
57 Bitmap for MSM8996 format:
64 Bitmap for MSM8996SG format (speedbin shifted of 4 left):
71 Bitmap for IPQ806x SoC:
|
| /Documentation/virt/kvm/x86/ |
| D | hypercalls.rst | 147 - a0: lower part of the bitmap of destination APIC IDs
148 - a1: higher part of the bitmap of destination APIC IDs
149 - a2: the lowest APIC ID in bitmap
155 bitmap contained in the first two arguments (a0 and a1). Bit 0 of
|
| /Documentation/hwmon/ |
| D | w83791d.rst | 107 A similar change has occurred for the bitmap corresponding to the alarms. The
108 original legacy method used a single sysfs alarms file containing a bitmap
119 specification as that avoids bitmap problems and is the preferred interface
149 Alarms bitmap vs. beep_mask bitmask
|