Searched full:chunk (Results 1 – 25 of 64) sorted by relevance
123
| /Documentation/admin-guide/device-mapper/ |
| D | dm-zoned.rst | 70 mapping of the logical device blocks. The mapping is done per chunk of
71 blocks, with the chunk size equal to the zoned block device size. The
72 mapping table is indexed by chunk number and each mapping entry
73 indicates the zone number of the device storing the chunk of data. Each
80 data chunk, a block is always valid only in the data zone mapping the
81 chunk or in the buffer zone of the chunk.
83 For a logical chunk mapped to a conventional zone, all write operations
86 write offset within the logical chunk is equal to the write pointer
90 conventional zone is allocated and assigned to the chunk being
91 accessed. Writing a block to the buffer zone of a chunk will
[all …]
|
| D | striped.rst | 11 Parameters: <num devs> <chunk size> [<dev path> <offset>]+
14 <chunk size>:
15 Size of each chunk of data. Must be at least as
24 be a multiple of the chunk size multiplied by the number of underlying devices.
34 # will be called "stripe_dev" and have a chunk-size of 128k.
|
| D | unstriped.rst | 14 <number of stripes> <chunk size> <stripe #> <dev_path> <offset>
19 <chunk size>
20 The amount of 512B sectors in the chunk striping.
48 CHUNK=256
52 DM_PARMS="0 ${RAID_SIZE} striped ${NUM} ${CHUNK}"
63 echo "0 1 unstriped ${NUM} ${CHUNK} ${i} /dev/mapper/raid0 0" | dmsetup create set-${i}
87 The current LBA model has a RAID 0 128k chunk on each core, resulting
127 unstriped on top of striped with 4 drives using 128K chunk size
|
| /Documentation/networking/ |
| D | oa-tc6-framework.rst | 47 read/write transfers. A chunk is the basic element of data transactions
49 each chunk. Ethernet frames are transferred over one or more data chunks.
64 Each transmit data chunk begins with a 32-bit data header followed by a
65 data chunk payload on MOSI. The data header indicates whether transmit
70 chunk consists of a data chunk payload ending with a 32-bit data footer.
161 transmit data chunk will have a 4 bytes header which contains the
163 transmit frame data within the 64 bytes data chunk payload.
168 | Tx Chunk |
170 | | 64 bytes chunk payload | | 4 bytes header | |------------>
179 1 - Data chunk
[all …]
|
| D | netconsole.rst | 269 For example, assuming a lot smaller chunk size, a message "the first
270 chunk, the 2nd chunk." may be split as follows::
272 6,416,1758426,-,ncfrag=0/31;the first chunk,
273 6,416,1758426,-,ncfrag=16/31; the 2nd chunk.
|
| D | xsk-tx-metadata.rst | 57 only the first chunk should carry the metadata.
|
| D | af_xdp.rst | 110 queue id of that netdev. It is created and configured (chunk size,
156 an example, if the UMEM is 64k and each chunk is 4k, then the UMEM has
162 running the application with aligned chunk mode, the kernel will mask
163 the incoming addr. E.g. for a chunk size of 2k, the log2(2048) LSB of
165 to the same chunk. If the user application is run in the unaligned
426 UMEM area that is 128K and a chunk size of 2K, this means that you
|
| /Documentation/admin-guide/ |
| D | pstore-blk.rst | 78 The chunk size in KB for oops/panic front-end. It **MUST** be a multiple of 4.
85 oldest chunk if there is no more free chunk.
90 The chunk size in KB for pmsg front-end. It **MUST** be a multiple of 4.
93 Unlike oops/panic front-end, there is only one chunk for pmsg front-end.
96 appended to the chunk. On reboot the contents are available in
102 The chunk size in KB for console front-end. It **MUST** be a multiple of 4.
105 Similar to pmsg front-end, there is only one chunk for console front-end.
107 All log of console will be appended to the chunk. On reboot the contents are
113 The chunk size in KB for ftrace front-end. It **MUST** be a multiple of 4.
117 depending on the count of cpu processors. Each chunk size is equal to
[all …]
|
| D | dell_rbu.rst | 32 image methods. In case of monolithic the driver allocates a contiguous chunk
75 The user creates packets header, gets the chunk of the BIOS image and
76 places it next to the packetheader; now, the packetheader + BIOS image chunk
|
| D | md.rst | 16 md=<md device no.>,<raid level>,<chunk size factor>,<fault level>,dev0,dev1,...,devn
55 ``chunk size factor``
60 Set the chunk size as 4k << n.
363 The size, in bytes, of the chunk which will be represented by a
|
| /Documentation/driver-api/mmc/ |
| D | mmc-async-req.rst | 72 request in two chunks, prepare the first chunk and start the request,
73 and finally prepare the second chunk and start the transfer.
83 * The first chunk of the request should take the same time
86 * the transfer is delayed, guesstimate max 4k as first chunk size.
95 * of the first chunk. If the MMC runs out of the first data chunk
|
| D | mmc-dev-attrs.rst | 73 hence "preferred_erase_size" provides a good chunk
|
| /Documentation/security/ |
| D | SCTP.rst | 26 Passes the ``@asoc`` and ``@chunk->skb`` of the association INIT packet to the
102 ASCONF chunk when the corresponding ``@optname``'s are present::
151 Respond to an INIT chunk.
165 Respond to an COOKIE ECHO chunk.
169 do the same as for INIT chunk Response.
204 Passes the ``@asoc`` and ``@chunk->skb`` of the association INIT packet to the
254 entries and also describes ASCONF chunk processing when Dynamic Address
|
| /Documentation/filesystems/ |
| D | erofs.rst | 70 - Support chunk-based data deduplication and rolling-hash compressed data
216 4 chunk-based file (v5.15+).
267 Chunk-based files
269 In order to support chunk-based data deduplication, a new inode data layout has
271 with ``extents`` area of the inode metadata indicating how to get the chunk
273 chunk index form (see struct erofs_inode_chunk_index in erofs_fs.h for more
276 By the way, chunk-based files are all uncompressed for now.
|
| /Documentation/fb/ |
| D | sh7760fb.rst | 13 * Framebuffer memory must be a large chunk allocated at the top
16 get a large enough contiguous chunk of memory.
|
| /Documentation/devicetree/bindings/net/ |
| D | microchip,lan8650.yaml | 39 Available, Transmit Chunk Credits Available and Extended Status
|
| /Documentation/netlink/specs/ |
| D | devlink.yaml | 531 name: region-chunk
533 nested-attributes: dl-region-chunk
535 name: region-chunk-data
538 name: region-chunk-addr
541 name: region-chunk-len
1139 name: region-chunk
1142 name: dl-region-chunk
1146 name: region-chunk-data
1148 name: region-chunk-addr
1812 - region-chunk-addr
[all …]
|
| /Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 19 which chunk writes have completed. If one of the not modified data disks of
|
| /Documentation/core-api/ |
| D | padata.rst | 161 finished. padata splits the job into units called chunks, where a chunk is a
167 call each time it assigns a job chunk to a thread. Then, define the thread
|
| D | memory-allocation.rst | 142 The maximal size of a chunk that can be allocated with `kmalloc` is
147 The address of a chunk allocated with `kmalloc` is aligned to at least
|
| D | assoc_array.rst | 122 1. Get a chunk of index key from caller data::
126 This should return a chunk of caller-supplied index key starting at the
132 2. Get a chunk of an object's index key::
342 The index key is read in chunks of machine word. Each chunk is subdivided into
|
| /Documentation/driver-api/ |
| D | pwrseq.rst | 28 A unit is a discreet chunk of a power sequence. For instance one unit may
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-reserved.rst | 210 The first plane can start either with JPEG or UYVY data chunk. The
212 multiplied by 2. The size of a JPEG chunk depends on the image and
|
| /Documentation/driver-api/dmaengine/ |
| D | provider.rst | 70 but all of them will require, for every chunk, at least the source and
231 deal with a single chunk to copy or a collection of them, here,
242 - A cyclic transfer is a transfer where the chunk collection will
655 - Chunk: A contiguous collection of bursts
|
| /Documentation/arch/arm64/ |
| D | kdump.rst | 21 large chunk of memomy can be found. The low memory reservation needs to
|
123