Searched full:back (Results 1 – 25 of 895) sorted by relevance
12345678910>>...36
| /Documentation/driver-api/md/ |
| D | raid5-cache.rst | 8 since 4.4) or write-back mode (supported since 4.10). mdadm (supported since
11 in write-through mode. A user can switch it to write-back mode by::
13 echo "write-back" > /sys/block/md0/md/journal_mode
15 And switch it back to write-through mode by::
30 tries to resync the array to bring it back to normal state. But before the
47 write-back mode
50 write-back mode fixes the 'write hole' issue too, since all write data is
51 cached on cache disk. But the main goal of 'write-back' cache is to speed up
56 overhead too. Write-back cache will aggregate the data and flush the data to
61 In write-back mode, MD reports IO completion to upper layer (usually
[all …]
|
| /Documentation/scsi/ |
| D | sd-parameters.txt | 12 write back | 1 0 | on | on
13 write back, no read (daft) | 1 1 | on | off
15 To set cache type to "write back" and save this setting to the drive:
17 # echo "write back" > cache_type
22 # echo "temporary write back" > cache_type
|
| /Documentation/fb/ |
| D | viafb.modes | 19 # Back Porch 1.907 us 1.048 ms
44 # Back Porch 3.810 us 0.427 ms
65 # Back Porch 2.222 us 0.578 ms
86 # Back Porch 2.409 us 0.475 ms
107 # Back Porch 1.984 us 0.496 ms
128 # Back Porch 3.274 us 0.462 ms
149 # Back Porch 3.245 us 435.949 us
170 # Back Porch 2.939 us 0.459 ms
191 # Back Porch 2.200 us 0.607 ms
213 # Back Porch 3.232 us 0.448 ms
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-bdi | 36 total write-back cache that relates to its current average
40 percentage of the write-back cache to a particular device.
46 given percentage of the write-back cache. This is useful in
48 most of the write-back cache. For example in case of an NFS
|
| D | sysfs-platform-hidma-mgmt | 63 read transactions that can be issued back to back.
84 write transactions that can be issued back to back.
|
| /Documentation/driver-api/ |
| D | dell_rbu.rst | 36 maintains a link list of packets for reading them back.
74 packets of data arranged back to back. It can be done as follows
79 image file and then arrange all these packets back to back in to one single
120 read back the image downloaded.
|
| /Documentation/devicetree/bindings/dma/ |
| D | qcom_hidma_mgmt.txt | 32 applied back to back while writing to the destination before yielding
35 applied back to back while reading the source before yielding the bus.
|
| /Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,idle-state.txt | 17 interrupt to trigger the core back in to active. This triggers the cache
41 back into Elevation Level (EL) which trampolines the control back to the
44 code in the EL for the SoC. On SoCs with write-back L1 cache, the cache has to
|
| /Documentation/devicetree/bindings/sound/ |
| D | fsl,asrc.txt | 5 output clock. The driver currently works as a Front End of DPCM with other Back
34 - fsl,asrc-rate : Defines a mutual sample rate used by DPCM Back Ends.
36 - fsl,asrc-width : Defines a mutual sample width used by DPCM Back Ends.
|
| /Documentation/cpu-freq/ |
| D | amd-powernow.txt | 34 and fall back to PST if that fails.
36 fall back to ACPI if the PSB support fails. A module parameter,
|
| /Documentation/powerpc/ |
| D | transactional_memory.rst | 18 guaranteed to either complete atomically or roll back and undo any partial
59 state will roll back to that at the 'tbegin', and control will continue from
153 the stack. It's possible that the stack has moved back up after the tbegin.
158 stack pointer will be back at the tbegin but our in memory stack won't be valid
166 signal will be rolled back anyway.
224 transaction to be aborted and rolled back. Kernel exceptions will also
225 cause the transaction to be aborted and rolled back and the exception
|
| D | dawr-power9.rst | 26 PPC_PTRACE_GETHWDBGINFO call. This results in GDB falling back to
49 host. The watchpoint will fail and GDB will fall back to software
58 migrated back to the POWER8 host, it will start working again.
|
| /Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 99 the CPU offline, then bring it back online. This forces
102 first one back online. Once you have onlined the CPUs in question,
104 timer back onto one of the CPUs in question.
116 bring it back online before you start your application.)
128 bring it back online before you start your application.)
140 bring it back online before you start your application.)
184 CPU offline, then bring it back online. This forces recurring
187 back online. Once you have onlined the CPUs in question, do not
189 back onto one of the CPUs in question.
|
| /Documentation/block/ |
| D | deadline-iosched.rst | 61 with a request that is already on the queue. Either it fits in the back of that
62 request, or it fits at the front. That is called either a back merge candidate
64 back merges are much more common than front merges. For some work loads, you
|
| /Documentation/vm/ |
| D | zswap.rst | 48 back into memory all of the pages stored in the compressed pool. The
50 either invalidated or faulted back into memory. In order to force all
52 fault back into memory all swapped out pages, including those in the
59 evict pages from its own compressed pool on an LRU basis and write them back to
|
| /Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 144 type of merge is often called a "back merge". Back merges can help to make
149 Why is that? Back merges will muddy the development history of your own
157 That said, back merges are occasionally required; when that happens, be
160 Even then, you should not back merge a tree above your immediate upstream
161 tree; if a higher-level back merge is really required, the upstream tree
169 merge conflicts than unnecessary back merges. Seeing the conflicts lets
|
| /Documentation/media/uapi/v4l/ |
| D | vidioc-enumaudioout.rst | 5 .. and no Back-Cover Texts. A copy of the license is included at
52 Connectors on a TV card to loop back the received audio signal
|
| D | vidioc-g-modulator.rst | 5 .. and no Back-Cover Texts. A copy of the license is included at
154 driver does not support stereo audio it shall fall back to mono.
165 return an ``EINVAL`` error code and the driver shall fall back to mono
187 driver shall fall back to mono or stereo mode.
|
| /Documentation/sound/hd-audio/ |
| D | models.rst | 8 3-jack in back and a headphone out
10 3-jack in back, a HP out and a SPDIF out
12 5-jack in back, 2-jack in front
14 5-jack in back, 2-jack in front, a SPDIF out
16 6-jack in back, 2-jack in front
412 3-jack in back
414 3-jack in back, 2-jack in front
416 6-jack in back, 2-jack in front
418 6-jack in back, 2-jack in front, SPDIF I/O
420 5-jack in back, 2-jack in front, SPDIF out
|
| /Documentation/devicetree/bindings/iommu/ |
| D | ti,omap-iommu.txt | 21 - ti,iommu-bus-err-back : Indicates the IOMMU instance supports throwing
22 back a bus error response on MMU faults.
|
| /Documentation/admin-guide/device-mapper/ |
| D | writecache.rst | 47 when writing data from persistent memory back to the
51 flag when writing back data and send the FLUSH request
|
| D | era.rst | 16 coherency after rolling back a vendor snapshot.
72 The scenario of invalidating a cache when rolling back a vendor
83 Rolling back to an vendor snapshot
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | da9062-wdt.txt | 17 Example: DA9061 using a fall-back compatible for the DA9062 watchdog driver
|
| /Documentation/x86/ |
| D | mtrr.rst | 73 reg00: base=0x00000000 ( 0MB), size= 128MB: write-back, count=1
74 reg01: base=0x08000000 ( 128MB), size= 64MB: write-back, count=1
87 reg00: base=0x00000000 ( 0MB), size= 128MB: write-back, count=1
88 reg01: base=0x08000000 ( 128MB), size= 64MB: write-back, count=1
124 reg00: base=0x00000000 ( 0MB), size= 64MB: write-back, count=1
209 "write-back", /* 6 */
309 "write-back", /* 6 */
|
| /Documentation/media/uapi/rc/ |
| D | rc-tables.rst | 5 .. and no Back-Cover Texts. A copy of the license is included at
151 - Instantly go back in time
153 - <<< / BACK
167 - Play movie back
650 - CANCEL / BACK
|
12345678910>>...36