Home
last modified time | relevance | path

Searched full:sequential (Results 1 – 25 of 249) sorted by relevance

12345678910

/linux/Documentation/admin-guide/device-mapper/
H A Ddm-zoned.rst9 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/Documentation/filesystems/
H A Dzonefs.rst12 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/tools/perf/pmu-events/arch/x86/elkhartlake/
H A Dfrontend.json56 …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…
74 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
/linux/tools/perf/pmu-events/arch/x86/snowridgex/
H A Dfrontend.json56 …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…
74 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
/linux/tools/perf/pmu-events/arch/x86/alderlaken/
H A Dfrontend.json16 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
25 …en accesses from sequential code crosses the cache line boundary, or when a branch target is moved…
/linux/include/linux/ns/
H A Dnstree_types.h12 * @ns_list_head: List head for sequential iteration
15 * and a list (for efficient sequential iteration). The list is kept in
26 * @ns_list_entry: List entry for sequential iteration
/linux/drivers/md/
H A Ddm-zoned-reclaim.c57 * 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()
H A Ddm-zoned-metadata.c57 /* The number of sequential zones reserved for reclaim */
88 * This zone may be sequential or random. If it is a sequential
1066 dmz_dev_err(dev, "Invalid number of reserved sequential zones"); in dmz_check_sb()
1610 * with the sequential write error flag.
1851 /* LRU rotate sequential zone */ in __dmz_lru_zone()
1992 * Select a buffered sequential zone for reclaim.
2019 * (1) There is no free sequential zones. Then a random data zone in dmz_get_zone_for_reclaim()
2020 * cannot be reclaimed. So choose a sequential zone to reclaim so in dmz_get_zone_for_reclaim()
2022 * (2) At least one free sequential zon in dmz_get_zone_for_reclaim()
[all...]
/linux/tools/testing/selftests/bpf/benchs/
H A Drun_bench_local_storage.sh11 summarize_local_storage "hashmap (control) sequential get: "\
19 summarize_local_storage "local_storage cache sequential get: "\
H A Dbench_local_storage.c241 /* 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
/linux/fs/zonefs/
H A Dzonefs.h25 * 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.
/linux/drivers/gpu/drm/mediatek/
H A Dmtk_hdmi_regs_v2.h238 * @DDC_CMD_SEQ_READ_NOACK: Sequential read with no ACK on last byte
239 * @DDC_CMD_SEQ_READ: Sequential read with ACK on last byte
242 * @DDC_CMD_SEQ_WRITE_NOACK: Sequential write ignoring ACK on last byte
243 * @DDC_CMD_SEQ_WRITE: Sequential write requiring ACK on last byte
/linux/Documentation/ABI/testing/
H A Dsysfs-driver-intel-m10-bmc22 of sequential MAC addresses assigned to the board
32 Description: Read only. Returns the number of sequential MAC
/linux/tools/perf/pmu-events/arch/x86/amdzen4/
H A Dcache.json448 … 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…
/linux/tools/perf/tests/
H A Dbuiltin-test.c48 static bool sequential; variable
517 if (pass == 1 && !sequential && test_exclusive(test, curr_test_case)) { in start_test()
521 if (pass != 1 && (sequential || !test_exclusive(test, curr_test_case))) { in start_test()
522 /* Sequential and non-exclusive tests were run on the first pass. */ in start_test()
543 if (sequential || pass == 2) { in start_test()
661 if (!sequential) { in __cmd_test()
796 OPT_BOOLEAN('S', "sequential", &sequential, in cmd_test()
837 sequential = true; in cmd_test()
/linux/arch/sh/include/asm/
H A Dsmp.h17 /* Map from cpu id to sequential logical cpu number. */
21 /* The reverse map from sequential logical cpu number to cpu id. */
/linux/tools/perf/pmu-events/arch/x86/grandridge/
H A Dfrontend.json20 …nts every time the code stream enters into a new cache line by walking sequential from the previou…
28 …nts every time the code stream enters into a new cache line by walking sequential from the previou…
/linux/arch/loongarch/include/asm/
H A Dsmp.h59 /* Map from cpu id to sequential logical cpu number. This will only
64 /* The reverse map from sequential logical cpu number to cpu id. */
/linux/arch/powerpc/platforms/pseries/
H A Dof_helpers.c75 /* 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/arch/mips/include/asm/
H A Dsmp.h38 /* Map from cpu id to sequential logical cpu number. This will only
43 /* The reverse map from sequential logical cpu number to cpu id. */
/linux/tools/testing/selftests/mm/
H A Dtest_vmalloc.sh75 echo "It runs all test cases on one single CPU with sequential order."
125 echo "sequential order"
/linux/tools/perf/pmu-events/arch/x86/sierraforest/
H A Dfrontend.json84 …nts every time the code stream enters into a new cache line by walking sequential from the previou…
92 …nts every time the code stream enters into a new cache line by walking sequential from the previou…
/linux/include/drm/bridge/
H A Dmhl.h360 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/Documentation/driver-api/md/
H A Draid5-cache.rst55 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/tools/perf/util/intel-pt-decoder/
H A Dintel-pt-decoder.h85 * The block type numbers are not sequential but here they are given sequential

12345678910