Searched full:block (Results 1 – 25 of 980) sorted by relevance
12345678910>>...40
| /Documentation/filesystems/ext4/ |
| D | blockgroup.rst | 6 The layout of a standard block group is approximately as follows (each
14 - ext4 Super Block
17 - Data Block Bitmap
22 - 1 block
25 - 1 block
26 - 1 block
30 For the special case of block group 0, the first 1024 bytes are unused,
32 The superblock will start at offset 1024 bytes, whichever block that
33 happens to be (usually 0). However, if for some reason the block size =
34 1024, then block 0 is marked in use and the superblock goes in block 1.
[all …]
|
| D | journal.rst | 34 consumes an entire block group, though mke2fs tries to put it in the
63 or a block revocation list. A finished transaction always ends with a
74 will be an ext4 super block in the usual place, with a matching UUID.
75 The journal superblock will be in the next full block after the
94 Block Header
97 Every block in the journal starts with a common 12-byte header
115 - Description of what this block contains. See the jbd2_blocktype_ table
120 - The transaction ID that goes with this block.
124 The journal block type can be any one of:
133 - Descriptor. This block precedes a series of data blocks that were
[all …]
|
| D | group_descr.rst | 3 Block Group Descriptors
6 Each block group on the filesystem has one of these descriptors
8 descriptors (if present) are the second item in the block group. The
9 standard configuration is for each block group to contain a full copy of
10 the block group descriptor table unless the sparse\_super feature flag
14 the inode table (i.e. they can float). This means that within a block
17 property to group several block groups into a flex group and lay out all
21 If the meta\_bg feature flag is set, then several block groups are
23 however, the first and last two block groups within the larger meta
30 block group descriptor was only 32 bytes long and therefore ends at
[all …]
|
| D | blocks.rst | 6 ext4 allocates storage space in units of “blocks”. A block is a group of
9 block groups. Block size is specified at mkfs time and typically is
10 4KiB. You may experience mounting problems if block size is greater than
14 of structures is stored in terms of the block number the structure lives
43 * - Blocks Per Block Group
48 * - Inodes Per Block Group
53 * - Block Group Size
63 * - Blocks Per File, Block Maps
73 * - File Size, Block Maps
105 * - Blocks Per Block Group
[all …]
|
| D | allocators.rst | 3 Block and Inode Allocation Policy
9 that the head actuator and disk must perform to access a data block,
13 effect of concentrating writes on a single erase block, which can speed
17 The first tool that ext4 uses to combat fragmentation is the multi-block
18 allocator. When a file is first created, the block allocator
23 files) then the file data gets written out in a single multi-block
33 file's data blocks in the same block group as its inode. This cuts down
39 same block group as the directory, when feasible. The working assumption
43 The fifth trick is that the disk volume is cut up into 128MB block
47 the block groups and puts that directory into the least heavily loaded
[all …]
|
| D | bigalloc.rst | 6 At the moment, the default size of a block is 4KiB, which is a commonly
8 ext4 code is not prepared to handle the case where the block size
15 use clustered allocation, so that each bit in the ext4 block allocation
19 This means that each bit in the block allocation bitmap now addresses
20 256 4k blocks. This shrinks the total size of the block allocation
22 means that a block group addresses 32 gigabytes instead of 128 megabytes,
25 The administrator can set a block cluster size at mkfs time (which is
27 on, the block bitmaps track clusters, not individual blocks. This means
28 that block groups can be several gigabytes in size (instead of just
30 block, even for directories. TaoBao had a patchset to extend the “use
|
| D | directory.rst | 11 such, directory entries are found by reading the data block(s)
22 data blocks and that each block contains a linear array of directory
23 entries. The end of each per-block array is signified by reaching the
24 end of the block; the last entry in the block has a record length that
25 takes it all the way to the end of the block. The end of the entire
116 - Block device file.
125 ``struct ext4_dir_entry`` is placed at the end of each leaf block to
159 - Directory leaf block checksum.
161 The leaf directory block checksum is calculated against the FS UUID, the
163 the entire directory entry block up to (but not including) the fake
[all …]
|
| D | bitmaps.rst | 3 Block and inode Bitmaps
6 The data block bitmap tracks the usage of data blocks within the block
12 block or inode table entry. This implies a block group size of 8 \*
15 NOTE: If ``BLOCK_UNINIT`` is set for a given block group, various parts
16 of the kernel and e2fsprogs code pretends that the block bitmap contains
25 Inode tables are statically allocated at mkfs time. Each block group
|
| D | ifork.rst | 8 regular files and directories will use it for file block indexing
15 string is less than 60 bytes long. Otherwise, either extents or block
18 Direct/Indirect Block Addressing
21 In ext2/3, file block numbers were mapped to logical block numbers by
22 means of an (up to) three level 1-1 block map. To find the logical block
23 that stores a particular file block, the code would navigate through
26 block isn't full of garbage.
36 Note that with this block mapping scheme, it is necessary to fill out a
46 In ext4, the file to logical block map has been replaced with an extent
48 requires an indirect block to map all 1,000 entries; with extents, the
[all …]
|
| D | attributes.rst | 7 block on the disk and referenced from inodes via ``inode.i_file_acl*``.
19 where extended attributes can be found is in the block pointed to by
21 block to contain a pointer to a second extended attribute block (or even
23 attribute's value to be stored in a separate data block, though as of
46 The beginning of an extended attribute block is in
76 - Checksum of the extended attribute block.
82 The checksum is calculated against the FS UUID, the 64-bit block number
83 of the extended attribute block, and the entire block (header +
89 long. When stored in an external block, the ``struct ext4_xattr_entry``
113 - Location of this attribute's value on the disk block where it is stored.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-block | 1 What: /sys/block/<disk>/stat
5 The /sys/block/<disk>/stat files displays the I/O
21 What: /sys/block/<disk>/<part>/stat
25 The /sys/block/<disk>/<part>/stat files display the
27 same as the above-written /sys/block/<disk>/stat
31 What: /sys/block/<disk>/integrity/format
35 Metadata format for integrity capable block device.
39 What: /sys/block/<disk>/integrity/read_verify
43 Indicates whether the block layer should verify the
48 What: /sys/block/<disk>/integrity/tag_size
[all …]
|
| D | sysfs-block-loop | 1 What: /sys/block/loopX/loop/autoclear
4 Contact: linux-block@vger.kernel.org
10 What: /sys/block/loopX/loop/backing_file
13 Contact: linux-block@vger.kernel.org
18 What: /sys/block/loopX/loop/offset
21 Contact: linux-block@vger.kernel.org
25 What: /sys/block/loopX/loop/sizelimit
28 Contact: linux-block@vger.kernel.org
30 (RO) The size (in bytes) that the block device maps, starting
33 What: /sys/block/loopX/loop/partscan
[all …]
|
| D | sysfs-block-zram | 1 What: /sys/block/zram<id>/disksize
10 What: /sys/block/zram<id>/initstate
17 What: /sys/block/zram<id>/reset
25 What: /sys/block/zram<id>/max_comp_streams
33 What: /sys/block/zram<id>/comp_algorithm
41 What: /sys/block/zram<id>/mem_used_max
51 What: /sys/block/zram<id>/mem_limit
60 What: /sys/block/zram<id>/compact
68 What: /sys/block/zram<id>/io_stat
73 statistics not accounted by block layer. For example,
[all …]
|
| D | sysfs-block-bcache | 1 What: /sys/block/<disk>/bcache/unregister
11 What: /sys/block/<disk>/bcache/clear_stats
17 What: /sys/block/<disk>/bcache/cache
24 What: /sys/block/<disk>/bcache/cache_hits
31 What: /sys/block/<disk>/bcache/cache_misses
37 What: /sys/block/<disk>/bcache/cache_hit_ratio
43 What: /sys/block/<disk>/bcache/sequential_cutoff
51 What: /sys/block/<disk>/bcache/bypassed
59 What: /sys/block/<disk>/bcache/writeback
68 What: /sys/block/<disk>/bcache/writeback_running
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-dust.txt | 15 in the "bad block list" will fail with EIO ("Input/output error").
17 Writes of blocks in the "bad block list will result in the following:
19 1. Remove the block from the "bad block list".
39 <device_path>: path to the block device.
41 <blksz>: block size in bytes
53 (For a device with a block size of 512 bytes)
56 (For a device with a block size of 4096 bytes)
75 At any time (i.e.: whether the device has the "bad block" emulation
80 kernel: device-mapper: dust: badblock added at block 60
83 kernel: device-mapper: dust: badblock added at block 67
[all …]
|
| D | dm-zoned.rst | 5 The dm-zoned device mapper target exposes a zoned block device (ZBC and
6 ZAC compliant devices) as a regular block device without any write
8 block device which hides from the user (a file system or an application
9 doing raw block device accesses) the sequential write constraints of
10 host-managed zoned block devices and can mitigate the potential
12 host-aware zoned block devices.
14 For a more detailed description of the zoned block device models and
38 write accesses to the sequential zones of a zoned block device.
55 irrespective of the physical sector size of the backend zoned block
61 1) The first block of the first conventional zone found contains the
[all …]
|
| D | cache.rst | 11 It aims to improve performance of a block device (eg, a spindle) by
32 Movement of the primary copy of a logical block from one
39 The origin device always contains a copy of the logical block, which
63 Fixed block size
66 The origin is divided up into blocks of a fixed size. This block size
68 using block sizes of 256KB - 1024KB. The block size must be between 64
71 Having a fixed block size simplifies the target a lot. But it is
72 something of a compromise. For instance, a small part of a block may be
73 getting hit a lot, yet the whole block will be promoted to the cache.
74 So large block sizes are bad because they waste cache space. And small
[all …]
|
| /Documentation/filesystems/ |
| D | sysv-fs.txt | 36 * Size of a block or zone (data allocation unit on disk)
42 * General layout: all have one boot block, one super block and
45 all the block numbers (including the super block) are offset by one track.
74 There is a cache of a certain number of free inodes in the super-block.
77 * Free block management:
81 since it is not true that every free block contains a pointer to
82 the next free block. Rather, the free blocks are organized in chunks
83 of limited size, and every now and then a free block contains pointers
85 contains pointers and so on. The list terminates with a "block number"
86 0 on Xenix FS and SystemV FS, with a block zeroed out on Coherent FS.
[all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpic-msgr.txt | 10 block. The type shall be <string-list> and the value shall be of the form
15 message register block's addressable register space. The type shall be
25 - mpic-msgr-receive-mask: Specifies what registers in the containing block
29 be <u32>. If not present, then all of the message registers in the block
34 An alias should be created for every message register block. They are not
37 'mpic-msgr-block<n>', where <n> is an integer specifying the block's number.
47 mpic_msgr_block0: mpic-msgr-block@41400 {
50 // Message registers 0 and 2 in this block can receive interrupts on
56 mpic_msgr_block1: mpic-msgr-block@42400 {
59 // Message registers 0 and 2 in this block can receive interrupts on
|
| /Documentation/admin-guide/blockdev/ |
| D | zram.rst | 2 zram: Compressed RAM based block devices
8 The zram module creates RAM based block devices named /dev/zram<id>
15 /sys/block/zram<id>/
55 echo 3 > /sys/block/zram0/max_comp_streams
85 cat /sys/block/zram0/max_comp_streams
98 cat /sys/block/zram0/comp_algorithm
102 echo lzo > /sys/block/zram0/comp_algorithm
122 echo $((50*1024*1024)) > /sys/block/zram0/disksize
125 echo 256K > /sys/block/zram0/disksize
126 echo 512M > /sys/block/zram0/disksize
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | dev-rds.rst | 114 - Least Significant Byte of RDS Block
117 - Most Significant Byte of RDS Block
119 - ``block``
120 - Block description
124 .. _v4l2-rds-block:
128 .. flat-table:: Block description
134 - Block (aka offset) of the received data.
140 block.
143 reception of this block.
147 .. _v4l2-rds-block-codes:
[all …]
|
| /Documentation/block/ |
| D | switching-sched.rst | 9 /sys/block/<device>/queue/iosched
16 It is possible to change the IO scheduler for a given block device on
22 echo SCHEDNAME > /sys/block/DEV/queue/scheduler
28 a "cat /sys/block/DEV/queue/scheduler" - the list of valid names
31 # cat /sys/block/sda/queue/scheduler
33 # echo none >/sys/block/sda/queue/scheduler
34 # cat /sys/block/sda/queue/scheduler
|
| D | queue-sysfs.rst | 6 for each block device. Note that stacked devices typically do not export
8 These files are the ones found in the /sys/block/xxx/queue/ directory.
20 This has different meaning depending on the type of the block device.
22 of the RAID volume stripe segment. For a zoned block device, either host-aware
62 Whether or not the block driver supports the FUA flag for write requests.
93 complete in this time then the block driver timeout handler is invoked.
104 This is the logical block size of the device, in bytes.
117 data that will be submitted by the block layer core to the associated
118 block driver.
122 This is the maximum number of kilobytes that the block layer will allow
[all …]
|
| /Documentation/devicetree/bindings/dma/ |
| D | fsl-qdma.txt | 24 - block-number: the virtual block number
25 - block-offset: the offset of different virtual block
26 - status-sizes: status queue size of per virtual block
27 - queue-sizes: command queue size of per virtual block, the size number
43 <0x0 0x838a000 0x0 0x2000>; /* Block regs */
50 block-number = <2>;
51 block-offset = <0x1000>;
|
| /Documentation/admin-guide/mm/ |
| D | memory-hotplug.rst | 85 size of a memory block is architecture dependent and represents the logical
87 default size of a memory block is the same as memory section size unless an
90 To determine the size (in bytes) of a memory block please read this file::
126 All memory blocks have their device information in sysfs. Each memory block
131 where XXX is the memory block id.
133 For the memory block covered by the sysfs directory. It is expected that all
137 block.
139 For example, assume 1GiB memory block size. A device for a memory starting at
146 Under each memory block, you can see 5 files:
155 ``phys_index`` read-only and contains memory block id, same as XXX.
[all …]
|
12345678910>>...40