Searched full:thin (Results 1 – 21 of 21) sorted by relevance
| /Documentation/networking/ |
| D | tcp-thin.rst | 4 Thin-streams and TCP
8 protocols display what we call thin-stream properties. This means
20 applications, we have seen that they often produce thin streams
27 for thin streams. In short, if the kernel detects a thin stream,
30 1) If the stream is thin, fast retransmit on the first dupACK.
31 2) If the stream is thin, do not apply exponential backoff.
34 thin. This is accomplished by defining a threshold for the number
50 "Improving latency for interactive, thin-stream applications over
|
| D | index.rst | 100 tcp-thin
|
| D | ip-sysctl.rst | 888 Enable dynamic triggering of linear timeouts for thin streams.
890 determine if the stream is thin (less than 4 packets in flight).
891 As long as the stream is found to be thin, up to 6 linear
894 non-aggressive thin streams, often found to be time-dependent.
895 For more information on thin streams, see
896 Documentation/networking/tcp-thin.rst
|
| /Documentation/admin-guide/device-mapper/ |
| D | thin-provisioning.rst | 2 Thin provisioning
9 between them implement thin-provisioning and snapshots.
51 This section describes some quick recipes for using thin provisioning.
63 - Function calls from the thin targets
78 are shared between thin devices (i.e. through snapshots). If you have
105 --table "0 20971520 thin-pool $metadata_dev $data_dev \
112 thin-pool is created. People primarily interested in thin provisioning
137 means the thin-provisioning target behaves like a physical disk that has
157 Thin provisioning
173 Thinly-provisioned volumes are activated using the 'thin' target::
[all …]
|
| D | persistent-data.rst | 13 - Heinz Mauelshagen's thin provisioning target
22 targets. It's currently used by the thin-provisioning target and an
83 thin-provisioning target uses a btree with two levels of nesting.
|
| D | dm-clone.rst | 29 The dm-clone target reuses the metadata library used by the thin-provisioning
309 or FUA bio is written, or periodically, like dm-thin and dm-cache do. This
316 4. Use dm-thin's external snapshot functionality. This approach is the most
327 thinly-provisioned volumes. Thin-provisioning has an inherent metadata
328 overhead, for maintaining the thin volume mappings, which significantly
331 Moreover, cloning a device shouldn't force the use of thin-provisioning. On
332 the other hand, if we wish to use thin provisioning, we can just use a thin
|
| D | index.rst | 34 thin-provisioning
|
| D | era.rst | 114 thin-provisioning-tools project:
116 https://github.com/jthornber/thin-provisioning-tools
|
| D | dm-init.rst | 59 `thin` constrained, requires dm target message from userspace
60 `thin-pool` constrained, requires dm target message from userspace
|
| D | cache.rst | 17 a thin-provisioning pool. Caching solutions that are integrated more
20 The target reuses the metadata library used in the thin-provisioning
|
| /Documentation/security/tpm/ |
| D | tpm_ftpm_tee.rst | 18 The driver acts as a thin layer that passes commands to and from a TPM
|
| /Documentation/devicetree/bindings/extcon/ |
| D | extcon-ptn5150.yaml | 13 PTN5150 is a small thin low power CC logic chip supporting the USB Type-C
|
| /Documentation/userspace-api/media/v4l/ |
| D | libv4l-introduction.rst | 10 libv4l is a collection of libraries which adds a thin abstraction layer
11 on top of video4linux2 devices. The purpose of this (thin) layer is to
|
| /Documentation/sound/soc/ |
| D | codec-to-codec.rst | 99 In order to trigger this dai_link widget, a thin codec driver for
|
| /Documentation/networking/device_drivers/ethernet/3com/ |
| D | 3c509.rst | 77 connector), not its AUI (thick-net) or 10base2 (thin-net/coax) interfaces.
116 3 10base2 (thin-net == coax / BNC connector)
|
| /Documentation/process/ |
| D | 2.Process.rst | 45 merge window do not come out of thin air; they have been collected, tested,
|
| /Documentation/block/ |
| D | bfq-iosched.rst | 292 queue. A very thin extra bandwidth is however guaranteed to
|
| /Documentation/dev-tools/ |
| D | kgdb.rst | 839 The kgdboc driver is actually a very thin driver that relies on the
|
| /Documentation/driver-api/usb/ |
| D | usb.rst | 193 usb_bus <usb_bus>` is a rather thin layer that became available
|
| /Documentation/kbuild/ |
| D | makefiles.rst | 172 This is a thin archive without a symbol table. It will be later
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 652 Description: This file shows the thin provisioning type. This is one of
|