Searched refs:sequential (Results 1 – 25 of 45) sorted by relevance
12
| /Linux-v4.19/Documentation/device-mapper/ |
| D | dm-zoned.txt | 8 doing raw block device accesses) the sequential write constraints of
36 dm-zoned implements an on-disk buffering scheme to handle non-sequential
37 write accesses to the sequential zones of a zoned block device.
47 sequential zones used exclusively to store user data. The conventional
50 later moved to a sequential zone so that the conventional zone can be
80 sequential zone, the write operation is processed directly only if the
82 offset within of the sequential data zone (i.e. the write operation is
87 automatically invalidate the same block in the sequential zone mapping
88 the chunk. If all blocks of the sequential zone become invalid, the zone
95 the sequential zone mapping a chunk, or if the chunk is buffered, from
[all …]
|
| D | cache-policies.txt | 121 sequential threshold set to 1024 and the random_threshold set to 8.
|
| /Linux-v4.19/Documentation/block/ |
| D | cfq-iosched.txt | 18 (for sequential workloads) and service trees (for random workloads) before
73 in higher end storage due to idle on sequential queue and allow dispatch
98 latency. But if sequential workload is higher(e.g. sequential read),
230 sequential reads (next read will come on only after completion of previous
232 did not move the disk head and kept on dispatching sequential IO from
239 All cfq queues doing synchronous sequential IO go on to sync-idle tree.
242 All synchronous non-sequential queues go on sync-noidle tree. Also any
264 queues. Otherwise in presence of many sequential readers, other
267 For example, if there are 10 sequential readers doing IO and they get
273 multiple sequential readers.
[all …]
|
| D | bfq-iosched.txt | 102 sequential workloads considered in our tests. With random workloads,
166 devices, if processes do synchronous and sequential I/O. In
207 performing random I/O that becomes mostly sequential if
251 associated with I/O-bound applications performing sequential
452 the percentage of sequential I/O requests issued. The price of larger
|
| /Linux-v4.19/Documentation/devicetree/bindings/timer/ |
| D | jcore,pit.txt | 8 there should be one region per cpu, indexed by the sequential,
|
| /Linux-v4.19/Documentation/devicetree/bindings/interrupt-controller/ |
| D | jcore,aic.txt | 10 region per cpu, indexed by the sequential, zero-based hardware cpu
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | bcache.rst | 31 to caching large sequential IO. Bcache detects sequential IO and skips it;
346 By default, bcache doesn't cache everything. It tries to skip sequential IO -
363 slower SSDs, many disks being cached by one SSD, or mostly sequential IO. So
369 cranking down the sequential bypass).
433 A sequential IO will bypass the cache once it passes this threshold; the
434 most recent 128 IOs are tracked so sequential IO can be detected even when
439 against all new requests to determine which new requests are sequential
440 continuations of previous requests for the purpose of determining sequential
441 cutoff. This is necessary if the sequential cutoff value is greater than the
442 maximum acceptable sequential size for any single request.
|
| /Linux-v4.19/Documentation/devicetree/bindings/net/can/ |
| D | xilinx_can.txt | 20 sequential Rx mode).
|
| /Linux-v4.19/Documentation/devicetree/bindings/display/ |
| D | ssd1307fb.txt | 22 - solomon,com-seq: Display uses sequential COM pin configuration
|
| /Linux-v4.19/drivers/md/bcache/ |
| D | request.c | 427 i->sequential = 0; in check_should_bypass()
429 if (i->sequential + bio->bi_iter.bi_size > i->sequential) in check_should_bypass()
430 i->sequential += bio->bi_iter.bi_size; in check_should_bypass()
434 task->sequential_io = i->sequential; in check_should_bypass()
|
| D | bcache.h | 288 unsigned int sequential; member
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-block-bcache | 47 For backing devices: Threshold past which sequential IO will
56 to the sequential cutoff). Expressed as bytes in human
|
| D | sysfs-fs-f2fs | 58 Controls the dirty page count condition for batched sequential
|
| D | sysfs-bus-rapidio | 193 sequential number (0 ... RIO_MAX_MPORTS) assigned to the mport
|
| /Linux-v4.19/Documentation/md/ |
| D | raid5-cache.txt | 53 which are sequential but not dispatched in the same time will suffer from this
57 typical workload which does sequential write followed by fsync is an example.
|
| /Linux-v4.19/Documentation/ |
| D | DMA-attributes.txt | 114 You might know that the accesses are likely to be sequential or
115 that they aren't sequential but it's unlikely you'll ping-pong
|
| /Linux-v4.19/Documentation/devicetree/bindings/net/ |
| D | apm-xgene-enet.txt | 22 - Must map to the first irq and irqs must be sequential
|
| /Linux-v4.19/Documentation/devicetree/bindings/sound/ |
| D | cs42l42.txt | 72 pressed, the driver will compare this biased voltage to sequential,
|
| /Linux-v4.19/Documentation/devicetree/bindings/memory-controllers/ |
| D | arm,pl172.txt | 79 - mpmc,page-mode-read-delay: Delay for asynchronous page mode sequential
|
| /Linux-v4.19/drivers/scsi/bfa/ |
| D | bfa_fc.h | 337 u32 sequential:1; member
341 u32 sequential:1;
|
| /Linux-v4.19/Documentation/filesystems/cifs/ |
| D | TODO | 100 there are some easy changes that can be done to parallelize sequential writes,
|
| /Linux-v4.19/Documentation/fb/ |
| D | udlfb.txt | 127 Where ? is the sequential framebuffer id of the particular DisplayLink device
|
| /Linux-v4.19/fs/squashfs/ |
| D | Kconfig | 196 performance for some file access patterns (e.g. sequential
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | mandatory-locking.txt | 31 cooperative file locking used to guarantee sequential access to files among
|
| /Linux-v4.19/Documentation/devicetree/bindings/arm/ |
| D | topology.txt | 91 sequential N value, starting from 0).
|
12
