| /linux-4.1.27/Documentation/device-mapper/ |
| D | cache-policies.txt | 49 The sequential threshold indicates the number of contiguous I/Os
50 required before a stream is treated as sequential. Once a stream is
51 considered sequential it will bypass the cache. The random threshold
55 The sequential and random thresholds default to 512 and 4 respectively.
57 Large, sequential I/Os are probably better left on the origin device
58 since spindles tend to have good sequential I/O bandwidth. The
60 of these sequential modes. But there are use-cases for wanting to
61 promote sequential blocks to the cache (e.g. fast application startup).
62 If sequential threshold is set to 0 the sequential I/O detection is
63 disabled and sequential I/O will no longer implicitly bypass the cache.
[all …]
|
| /linux-4.1.27/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
99 latency. But if sequential workload is higher(e.g. sequential read),
231 sequential reads (next read will come on only after completion of previous
233 did not move the disk head and kept on dispatching sequential IO from
240 All cfq queues doing synchronous sequential IO go on to sync-idle tree.
243 All synchronous non-sequential queues go on sync-noidle tree. Also any
265 queues. Otherwise in presence of many sequential readers, other
268 For example, if there are 10 sequential readers doing IO and they get
274 multiple sequential readers.
[all …]
|
| /linux-4.1.27/Documentation/ |
| D | bcache.txt | 26 to caching large sequential IO. Bcache detects sequential IO and skips it;
147 By default, bcache doesn't cache everything. It tries to skip sequential IO -
164 slower SSDs, many disks being cached by one SSD, or mostly sequential IO. So
170 cranking down the sequential bypass).
232 A sequential IO will bypass the cache once it passes this threshold; the
233 most recent 128 IOs are tracked so sequential IO can be detected even when
238 against all new requests to determine which new requests are sequential
239 continuations of previous requests for the purpose of determining sequential
240 cutoff. This is necessary if the sequential cutoff value is greater than the
241 maximum acceptable sequential size for any single request.
|
| D | crc32.txt | 155 But this still enforces sequential execution: a second group of table
|
| D | vme_api.txt | 61 Here, the 'num' field refers to the sequential device ID for this specific
|
| D | DMA-API-HOWTO.txt | 359 and for which hardware can optimize for sequential accesses.
|
| D | memory-barriers.txt | 2469 appropriately sequential. Whilst this, for the most part, renders the explicit
|
| /linux-4.1.27/Documentation/blockdev/ |
| D | cciss.txt | 94 SCSI sequential access devices and medium changer devices are supported and
117 Note also that if no sequential access devices or medium changers are
133 driver to make note of any new or removed sequential access devices
143 Note: ONLY sequential access devices and medium changers are presented
|
| /linux-4.1.27/drivers/md/bcache/ |
| D | request.c | 415 i->sequential = 0; in check_should_bypass()
417 if (i->sequential + bio->bi_iter.bi_size > i->sequential) in check_should_bypass()
418 i->sequential += bio->bi_iter.bi_size; in check_should_bypass()
422 task->sequential_io = i->sequential; in check_should_bypass()
|
| D | bcache.h | 301 unsigned sequential; member
|
| /linux-4.1.27/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
|
| /linux-4.1.27/drivers/scsi/bfa/ |
| D | bfa_fc.h | 336 u32 sequential:1; member
340 u32 sequential:1;
|
| D | bfa_fcbuild.c | 105 plogi_tmpl.class3.sequential = 1; in fcbuild_init()
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | TODO | 100 there are some easy changes that can be done to parallelize sequential writes,
|
| D | README | 447 client (e.g. when the application is doing large sequential
|
| /linux-4.1.27/Documentation/rapidio/ |
| D | sysfs.txt | 103 RapidIO destination ID) into this file. The mport_ID is a sequential
|
| D | rapidio.txt | 224 sequential number (0 ... RIO_MAX_MPORTS) assigned during mport device
|
| /linux-4.1.27/fs/squashfs/ |
| D | Kconfig | 182 performance for some file access patterns (e.g. sequential
|
| /linux-4.1.27/Documentation/fb/ |
| D | udlfb.txt | 127 Where ? is the sequential framebuffer id of the particular DisplayLink device
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | debugfs.txt | 125 another to insert a register block in the middle of another sequential
|
| D | mandatory-locking.txt | 31 cooperative file locking used to guarantee sequential access to files among
|
| D | f2fs.txt | 543 for devices showing very good sequential write performance, since free segments
|
| D | proc.txt | 462 sr - sequential read advise provided
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | topology.txt | 91 sequential N value, starting from 0).
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | net.txt | 301 originally may have been issued in the correct sequential order.
|
| /linux-4.1.27/scripts/ |
| D | spelling.txt | 866 sequencial||sequential
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | blkio-controller.txt | 365 On a faster hardware CFQ can be slow, especially with sequential workload.
|
| /linux-4.1.27/Documentation/mtd/ |
| D | nand_ecc.txt | 574 Furthermore there are 4 sequential assignments to rp8. This can be
|
| /linux-4.1.27/Documentation/trace/ |
| D | ftrace.txt | 107 sequential reads to display more current data. Once
109 will not be read again with a sequential read. The
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ChangeLog.lpfc | 1132 * Allow for board numbers that are not sequential, paving the way
|
| /linux-4.1.27/Documentation/networking/ |
| D | bonding.txt | 515 Round-robin policy: Transmit packets in sequential
|