| /linux/Documentation/admin-guide/device-mapper/ |
| 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
106 be exhausted (all used to map chunks or buffer sequential zones) and
110 blocks of the buffer zone to a free sequential zone. Once the copy
[all …]
|
| /linux/Documentation/filesystems/ |
| 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
41 sequentially. Each sequential zone has a write pointer maintained by the
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.
146 on sequential files. Only direct I/O writes are accepted for these files.
201 enforces sequential file write for sequential zones, unaligned write errors
204 If one of the write request within the set of sequential write requests
378 sequential zone files. Failure to do so can result in write errors.
380 sequential zone files that are in an active state, that is, sequential zone
[all …]
|
| /linux/tools/perf/tests/ |
| A D | builtin-test.c | 43 static bool sequential = true; variable
381 if (err || !sequential) in start_test()
467 if (!sequential) { in __cmd_test()
544 OPT_BOOLEAN('S', "sequential", &sequential, in cmd_test()
573 sequential = true; in cmd_test()
575 sequential = false; in cmd_test()
|
| /linux/tools/perf/Documentation/ |
| A D | perf-test.txt | 35 --sequential::
47 sets sequential mode.
|
| A D | db-export.txt | 15 The export process provides records with unique sequential ids which allows the
|
| /linux/Documentation/ABI/testing/ |
| 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
|
| A 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/Documentation/devicetree/bindings/interrupt-controller/ |
| A D | jcore,aic.txt | 10 region per cpu, indexed by the sequential, zero-based hardware cpu
|
| /linux/Documentation/devicetree/bindings/timer/ |
| A D | jcore,pit.txt | 8 there should be one region per cpu, indexed by the sequential,
|
| /linux/tools/perf/ |
| A D | Makefile | 55 BUILD_TYPE := sequential
|
| /linux/Documentation/devicetree/bindings/clock/ |
| A D | nuvoton,ma35d1-clk.yaml | 37 EPLL, and VPLL in sequential.
|
| /linux/Documentation/admin-guide/ |
| 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.
|
| /linux/Documentation/driver-api/mmc/ |
| A D | mmc-test.rst | 204 | 23 | Best-case read performance | Performs 512K sequential read (non sg) |
230 | 35 | Large sequential read | Into scattered pages |
232 | 36 | Large sequential write | From scattered pages |
|
| /linux/drivers/md/bcache/ |
| A D | request.c | 438 i->sequential = 0; in check_should_bypass()
440 if (i->sequential + bio->bi_iter.bi_size > i->sequential) in check_should_bypass()
441 i->sequential += bio->bi_iter.bi_size; in check_should_bypass()
445 task->sequential_io = i->sequential; in check_should_bypass()
|
| /linux/Documentation/core-api/ |
| A 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/Documentation/devicetree/bindings/net/can/ |
| A D | xilinx,can.yaml | 43 description: CAN Rx fifo depth (Zynq, Axi CAN, CAN FD in sequential Rx mode)
|
| /linux/Documentation/driver-api/md/ |
| A 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/Documentation/devicetree/bindings/net/ |
| A D | apm-xgene-enet.txt | 22 - Must map to the first irq and irqs must be sequential
|
| /linux/Documentation/block/ |
| A D | blk-mq.rst | 76 to sequential access, grouped requests for sequential access decreases the
|
| A D | bfq-iosched.rst | 122 sequential workloads considered in our tests. With random workloads,
187 devices, if processes do synchronous and sequential I/O. In
228 performing random I/O that becomes mostly sequential if
272 associated with I/O-bound applications performing sequential
480 the percentage of sequential I/O requests issued. The price of larger
|
| /linux/Documentation/devicetree/bindings/memory-controllers/ |
| A D | arm,pl172.txt | 79 - mpmc,page-mode-read-delay: Delay for asynchronous page mode sequential
|
| /linux/drivers/scsi/bfa/ |
| A D | bfa_fc.h | 314 u32 sequential:1; member
318 u32 sequential:1;
|
| /linux/Documentation/devicetree/bindings/display/ |
| A D | solomon,ssd1307fb.yaml | 56 Display uses sequential COM pin configuration
|
| /linux/Documentation/admin-guide/media/ |
| A D | imx.rst | 217 pad's field type is sequential top-bottom or bottom-top, and the
472 must output sequential or alternating fields (field type 'seq-bt' for
493 Compensated de-interlacing. The adv7180 must output sequential or
530 must output sequential or alternating fields (field type 'seq-bt' for
551 Compensated de-interlacing. The adv7180 must output sequential or
|
| /linux/Documentation/devicetree/bindings/dma/ |
| A D | fsl,edma.yaml | 109 # instead, you can simply maintain the sequential IRQ numbers as
|