| /Linux-v6.1/Documentation/admin-guide/device-mapper/ |
| D | dm-zoned.rst | 9 doing raw block device accesses) the sequential write constraints of
37 dm-zoned implements an on-disk buffering scheme to handle non-sequential
38 write accesses to the sequential zones of a zoned block device.
52 sequential zones used exclusively to store user data. The conventional
55 later moved to a sequential zone so that the conventional zone can be
85 sequential zone, the write operation is processed directly only if the
87 offset within of the sequential data zone (i.e. the write operation is
92 automatically invalidate the same block in the sequential zone mapping
93 the chunk. If all blocks of the sequential zone become invalid, the zone
100 the sequential zone mapping a chunk, or if the chunk is buffered, from
[all …]
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | zonefs.rst | 12 device support (e.g. f2fs), zonefs does not hide the sequential write
13 constraint of zoned block devices to the user. Files representing sequential
40 * Sequential zones: these zones accept random reads but must be written
41 sequentially. Each sequential zone has a write pointer maintained by the
43 to the device. As a result of this write constraint, LBAs in a sequential zone
44 cannot be overwritten. Sequential zones must first be erased using a special
78 the zone containing the super block is a sequential zone, the mkzonefs format
94 For sequential write zones, the sub-directory "seq" is used.
132 Sequential zone files
135 The size of sequential zone files grouped in the "seq" sub-directory represents
[all …]
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/elkhartlake/ |
| D | frontend.json | 77 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
89 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
101 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/snowridgex/ |
| D | frontend.json | 77 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
89 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
101 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
|
| /Linux-v6.1/fs/zonefs/ |
| D | zonefs.h | 25 * Zone types: ZONEFS_ZTYPE_SEQ is used for all sequential zone types
59 /* File zone write pointer position (sequential zones only) */
70 * sequential file truncation, two locks are used. For serializing
75 * a sequential file size on completion of direct IO writes.
|
| D | super.c | 169 * Sequential zones can only accept direct writes. This is already in zonefs_write_iomap_begin()
178 * For conventional zones, all blocks are always mapped. For sequential in zonefs_write_iomap_begin()
482 * sequential zone, the zone write pointer position must also be checked to
542 * Only sequential zone files can be truncated and truncation is allowed in zonefs_file_truncate()
659 * Since only direct writes are allowed in sequential files, page cache in zonefs_file_fsync()
711 * shared writable mappings. For sequential zone files, only read in zonefs_file_mmap()
731 * and below the zone write pointer for sequential zones. In both in zonefs_file_llseek()
886 * Handle direct writes. For sequential zone files, this is the only possible
889 * delivers write requests to the device in sequential order. This is always the
905 * For async direct IOs to sequential zone files, refuse IOCB_NOWAIT in zonefs_file_dio_write()
[all …]
|
| /Linux-v6.1/drivers/md/ |
| D | dm-zoned-reclaim.c | 57 * Align a sequential zone write pointer to chunk_block.
155 * If we are writing in a sequential zone, we must make sure in dmz_reclaim_copy()
156 * that writes are sequential. So Zeroout any eventual hole in dmz_reclaim_copy()
277 * Move valid blocks of the random data zone dzone into a free sequential zone.
278 * Once blocks are moved, remap the zone chunk to the sequential zone.
288 /* Get a free random or sequential zone */ in dmz_reclaim_rnd_data()
307 /* Flush the random data zone into the sequential zone */ in dmz_reclaim_rnd_data()
317 /* Free the sequential zone */ in dmz_reclaim_rnd_data()
391 * valid data blocks to a free sequential zone. in dmz_do_reclaim()
|
| /Linux-v6.1/tools/testing/selftests/bpf/benchs/ |
| D | run_bench_local_storage.sh | 11 summarize_local_storage "hashmap (control) sequential get: "\
19 summarize_local_storage "local_storage cache sequential get: "\
|
| D | bench_local_storage.c | 246 /* cache sequential and interleaved get benchs test local_storage get
250 * cache sequential get: call bpf_task_storage_get on n maps in order
251 * cache interleaved get: like "sequential get", but interleave 4 calls to the
|
| /Linux-v6.1/mm/ |
| D | readahead.c | 32 * a subsequent readahead. Once a series of sequential reads has been
52 * discovered from the struct file_ra_state for simple sequential reads,
54 * sequential reads are interleaved. Specifically: where the readahead
69 * reads from there are often sequential. There are other minor
392 * In interleaved sequential reads, concurrent streams on the same fd can
401 * for sequential patterns. Hence interleaved reads might be served as
402 * sequential ones.
416 * - length of the sequential read sequence, or
564 * A minimal readahead algorithm for trivial sequential/random reads.
591 * It's the expected callback index, assume sequential access. in ondemand_readahead()
[all …]
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | bcache.rst | 34 to caching large sequential IO. Bcache detects sequential IO and skips it;
353 By default, bcache doesn't cache everything. It tries to skip sequential IO -
370 slower SSDs, many disks being cached by one SSD, or mostly sequential IO. So
376 cranking down the sequential bypass).
440 A sequential IO will bypass the cache once it passes this threshold; the
441 most recent 128 IOs are tracked so sequential IO can be detected even when
446 against all new requests to determine which new requests are sequential
447 continuations of previous requests for the purpose of determining sequential
448 cutoff. This is necessary if the sequential cutoff value is greater than the
449 maximum acceptable sequential size for any single request.
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/meteorlake/ |
| D | frontend.json | 3 …nts every time the code stream enters into a new cache line by walking sequential from the previou…
14 …nts every time the code stream enters into a new cache line by walking sequential from the previou…
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-driver-intel-m10-bmc | 22 of sequential MAC addresses assigned to the board
32 Description: Read only. Returns the number of sequential MAC
|
| D | sysfs-block-bcache | 47 For backing devices: Threshold past which sequential IO will
56 to the sequential cutoff). Expressed as bytes in human
|
| /Linux-v6.1/arch/sh/include/asm/ |
| D | smp.h | 17 /* Map from cpu id to sequential logical cpu number. */
21 /* The reverse map from sequential logical cpu number to cpu id. */
|
| /Linux-v6.1/arch/loongarch/include/asm/ |
| D | smp.h | 51 /* Map from cpu id to sequential logical cpu number. This will only
56 /* The reverse map from sequential logical cpu number to cpu id. */
|
| /Linux-v6.1/arch/powerpc/platforms/pseries/ |
| D | of_helpers.c | 75 /* Get number-sequential-elements:encode-int */ in of_read_drc_info_cell()
80 /* Get sequential-increment:encode-int */ in of_read_drc_info_cell()
|
| /Linux-v6.1/arch/mips/include/asm/ |
| D | smp.h | 40 /* Map from cpu id to sequential logical cpu number. This will only
45 /* The reverse map from sequential logical cpu number to cpu id. */
|
| /Linux-v6.1/tools/testing/selftests/vm/ |
| D | test_vmalloc.sh | 53 echo "It runs all test cases on one single CPU with sequential order."
100 echo "sequential order"
|
| /Linux-v6.1/include/drm/bridge/ |
| D | mhl.h | 360 MHL3_3D_FORMAT_TYPE_FS, /* frame sequential */
363 MHL3_3D_FORMAT_TYPE_FS_TB, /* frame sequential, top-bottom */
364 MHL3_3D_FORMAT_TYPE_FS_LR, /* frame sequential, left-right */
|
| /Linux-v6.1/Documentation/core-api/ |
| D | dma-attributes.rst | 88 You might know that the accesses are likely to be sequential or
89 that they aren't sequential but it's unlikely you'll ping-pong
|
| /Linux-v6.1/Documentation/driver-api/md/ |
| D | raid5-cache.rst | 55 which are sequential but not dispatched in the same time will suffer from this
59 typical workload which does sequential write followed by fsync is an example.
|
| /Linux-v6.1/Documentation/devicetree/bindings/timer/ |
| D | jcore,pit.txt | 8 there should be one region per cpu, indexed by the sequential,
|
| /Linux-v6.1/Documentation/devicetree/bindings/interrupt-controller/ |
| D | jcore,aic.txt | 10 region per cpu, indexed by the sequential, zero-based hardware cpu
|
| /Linux-v6.1/tools/include/uapi/linux/ |
| D | fadvise.h | 7 #define POSIX_FADV_SEQUENTIAL 2 /* Expect sequential page references. */
|
