| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/filesystems/ |
| H A 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 …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/elkhartlake/ |
| H A D | frontend.json | 49 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
57 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
65 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/snowridgex/ |
| H A D | frontend.json | 49 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
57 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
65 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/alderlaken/ |
| H A D | frontend.json | 14 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
22 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 046 | 94 # Sequential write case: Alloc middle of cluster 2, then write overlapping
115 # Sequential write, but the next cluster is already allocated
127 # Sequential write, but the next cluster is already allocated
143 # Sequential write, and the next cluster is compressed
158 # Reverse sequential write
168 # Reverse sequential write with a gap
|
| H A D | 250 | 48 # To reproduce bug we need to overflow int by one sequential discard, so we
50 # of 512M sequential data, corresponding to one L1 entry), and we need some
|
| /openbmc/linux/fs/zonefs/ |
| H A D | file.c | 78 * Sequential zones can only accept direct writes. This is already in zonefs_write_iomap_begin()
86 * For conventional zones, all blocks are always mapped. For sequential in zonefs_write_iomap_begin()
196 * Only sequential zone files can be truncated and truncation is allowed in zonefs_file_truncate()
267 * Since only direct writes are allowed in sequential files, page cache in zonefs_file_fsync()
318 * shared writable mappings. For sequential zone files, only read in zonefs_file_mmap()
338 * and below the zone write pointer for sequential zones. In both in zonefs_file_llseek()
447 * Handle direct writes. For sequential zone files, this is the only possible
450 * delivers write requests to the device in sequential order. This is always the
465 * For async direct IOs to sequential zone files, refuse IOCB_NOWAIT in zonefs_file_dio_write()
491 /* Enforce sequential writes (append only) in sequential zones */ in zonefs_file_dio_write()
[all …]
|
| H A D | zonefs.h | 25 * Zone types: ZONEFS_ZTYPE_SEQ is used for all sequential zone types
65 /* Write pointer offset in the zone (sequential zones only, bytes) */
92 * sequential file truncation, two locks are used. For serializing
97 * a sequential file size on completion of direct IO writes.
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/grandridge/ |
| H A D | frontend.json | 3 …nts every time the code stream enters into a new cache line by walking sequential from the previou…
10 …nts every time the code stream enters into a new cache line by walking sequential from the previou…
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/sierraforest/ |
| H A D | frontend.json | 3 …nts every time the code stream enters into a new cache line by walking sequential from the previou…
10 …nts every time the code stream enters into a new cache line by walking sequential from the previou…
|
| /openbmc/linux/drivers/md/ |
| H A 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()
|
| /openbmc/linux/tools/testing/selftests/bpf/benchs/ |
| H A D | run_bench_local_storage.sh | 11 summarize_local_storage "hashmap (control) sequential get: "\
19 summarize_local_storage "local_storage cache sequential get: "\
|
| H A D | bench_local_storage.c | 241 /* cache sequential and interleaved get benchs test local_storage get
245 * cache sequential get: call bpf_task_storage_get on n maps in order
246 * cache interleaved get: like "sequential get", but interleave 4 calls to the
|
| /openbmc/linux/mm/ |
| H A 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
391 * In interleaved sequential reads, concurrent streams on the same fd can
400 * for sequential patterns. Hence interleaved reads might be served as
401 * sequential ones.
415 * - length of the sequential read sequence, or
549 * A minimal readahead algorithm for trivial sequential/random reads.
576 * It's the expected callback index, assume sequential access. in ondemand_readahead()
[all …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A 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.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A 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
|
| /openbmc/linux/arch/sh/include/asm/ |
| H A 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. */
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/amdzen4/ |
| H A D | cache.json | 448 … pipeline which hit in the L2 cache of type L2Stream (fetch additional sequential lines into L2 ca…
466 …ich hit in the L2 cache of type L2Burst (aggressively fetch additional sequential lines into L2 ca…
478 … pipeline which hit in the L2 cache of type L1Stream (fetch additional sequential lines into L1 ca…
502 …he L2 cache and hit in the L3 cache of type L2Stream (fetch additional sequential lines into L2 ca…
520 …and hit in the L3 cache of type L2Burst (aggressively fetch additional sequential lines into L2 ca…
532 …he L2 cache and hit in the L3 cache of type L1Stream (fetch additional sequential lines into L1 ca…
556 …which miss the L2 and the L3 caches of type L2Stream (fetch additional sequential lines into L2 ca…
574 …he L2 and the L3 caches of type L2Burst (aggressively fetch additional sequential lines into L2 ca…
586 …which miss the L2 and the L3 caches of type L1Stream (fetch additional sequential lines into L1 ca…
|
| /openbmc/linux/arch/loongarch/include/asm/ |
| H A 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. */
|
| /openbmc/linux/arch/powerpc/platforms/pseries/ |
| H A 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()
|
| /openbmc/linux/arch/mips/include/asm/ |
| H A 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. */
|
| /openbmc/qemu/docs/devel/ |
| H A D | zoned-storage.rst | 6 that are larger than the LBA size. They can only allow sequential writes, which
15 - BLK_Z_HM: The host-managed zoned model only allows sequential writes access
|
| /openbmc/qemu/scripts/simplebench/ |
| H A D | bench_prealloc.py | 118 'id': f'{name}, aligned sequential 16k',
123 'id': f'{name}, unaligned sequential 64k',
|
| /openbmc/linux/tools/testing/selftests/mm/ |
| H A D | test_vmalloc.sh | 53 echo "It runs all test cases on one single CPU with sequential order."
100 echo "sequential order"
|