Searched full:back (Results 1 – 25 of 637) sorted by relevance
12345678910>>...26
| /Documentation/ABI/testing/ |
| D | sysfs-class-bdi | 38 total write-back cache that relates to its current average
42 percentage of the write-back cache to a particular device.
52 total write-back cache that relates to its current average
56 of the write-back cache to a particular device. The value is
67 given percentage of the write-back cache. This is useful in
69 most of the write-back cache. For example in case of an NFS
80 given value of the write-back cache. The value is given as part
82 one device taking all or most of the write-back cache. For example
93 total write-back cache that relates to its current average
97 percentage of the write-back cache to a particular device
[all …]
|
| D | sysfs-bus-surface_aggregator-tabletsw | 18 - "folded-canvas": The type-cover has been folded back
19 part-ways, but does not lie flush with the back side of the
23 - "folded-back": The type cover has been fully folded back and
24 lies flush with the back side of the device.
47 back and the device operates mainly based on touch input.
|
| D | debugfs-scmi-raw | 12 and sent while the replies are read back one message at time
30 and sent while the replies are read back one message at time
41 Each read gives back one message at time (receiving an EOF at
52 Each read gives back one message at time (receiving an EOF at
81 and sent while the replies are read back one message at time
108 and sent while the replies are read back one message at time
|
| 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.
|
| D | sysfs-bus-most | 220 This is to read back the configured number of buffers of
229 This is to read back the configured buffer size of the channel.
237 This is to read back the configured direction of the channel.
249 This is to read back the configured data type of the channel.
263 This is to read back the configured subbuffer size of
272 This is to read back the configured number of packets per
|
| /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.rst | 16 write back 1 0 on on
17 write back, no read (daft) 1 1 on off
20 To set cache type to "write back" and save this setting to the drive::
22 # echo "write back" > cache_type
27 # echo "temporary write back" > cache_type
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-pisp-be.rst | 9 Raspberry Pi PiSP Back End configuration format
12 The Raspberry Pi PiSP Back End memory-to-memory image signal processor is
17 The PiSP Back End processes images in tiles, and its configuration requires
23 provide detailed description of the ISP back end configuration and programming
48 Raspberry Pi PiSP Back End uAPI data types
52 PiSP Back End. The section is informative only, for a detailed description of
|
| /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/admin-guide/media/ |
| D | raspberrypi-pisp-be.rst | 4 Raspberry Pi PiSP Back End Memory-to-Memory ISP (pisp-be)
7 The PiSP Back End
10 The PiSP Back End is a memory-to-memory Image Signal Processor (ISP) which reads
13 pixel data back to memory through two distinct output channels.
18 The PiSP Back End ISP processes images in tiles. The handling of image
25 in DRAM memory and processing them in the PiSP Back End to obtain images usable
32 The Raspberry Pi PiSP Back End (pisp-be) driver is located under
|
| /Documentation/admin-guide/ |
| 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.
|
| 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.
|
| D | quickly-build-trimmed-linux.rst | 79 quickly look something up in the reference section and afterwards jump back
286 First, switch back into the sources tree::
379 [:ref:`back to step-by-step guide <backup_sbs>`]
416 [:ref:`back to step-by-step guide <secureboot_sbs>`]
462 [:ref:`back to step-by-step guide <buildrequires_sbs>`]
480 [:ref:`back to step-by-step guide <diskspace_sbs>`]
504 [:ref:`back to step-by-step guide <sources_sbs>`]
546 [:ref:`back to step-by-step guide <sources_sbs>`] [:ref:`back to section intro <sources>`]
577 [:ref:`back to step-by-step guide <sources_sbs>`] [:ref:`back to section intro <sources>`]
600 [:ref:`back to step-by-step guide <sources_sbs>`] [:ref:`back to section intro <sources>`]
[all …]
|
| /Documentation/sphinx/ |
| D | parallel-wrapper.sh | 5 # environment (as exported by scripts/jobserver-exec), or fall back to
15 # fall back to the expected "-jauto" mode that the "htmldocs"
|
| /Documentation/devicetree/bindings/media/ |
| D | raspberrypi,pispbe.yaml | 7 title: Raspberry Pi PiSP Image Signal Processor (ISP) Back End
14 The Raspberry Pi PiSP Image Signal Processor (ISP) Back End is an image
|
| /Documentation/devicetree/bindings/sound/ |
| D | fsl,imx-asrc.yaml | 13 with other Back Ends Audio controller such as ESAI, SSI and SAI. It has
82 description: The mutual sample rate used by DPCM Back Ends
86 description: The mutual sample width used by DPCM Back Ends
107 Defines a mutual sample format used by DPCM Back Ends, which can
|
| /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/userspace-api/ |
| D | tee.rst | 37 clients, forward them to the TEE and send back the results. In the case of
39 requests to the supplicant which then sends back the result.
|
| /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/arch/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 | 34 PPC_PTRACE_GETHWDBGINFO call. This results in GDB falling back to
57 host. The watchpoint will fail and GDB will fall back to software
66 migrated back to the POWER8 host, it will start working again.
|
| /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
416 3-jack in back
418 3-jack in back, 2-jack in front
420 6-jack in back, 2-jack in front
422 6-jack in back, 2-jack in front, SPDIF I/O
424 5-jack in back, 2-jack in front, SPDIF out
|
| /Documentation/devicetree/bindings/input/ |
| D | goodix,gt7375p.yaml | 55 Due to potential touchscreen hardware flaw, back-powering could happen in
57 This property is used to avoid the back-powering issue.
|
| /Documentation/i2c/ |
| D | i2c-address-translators.rst | 78 with address translated back to 0x20
81 - Slave X driver gets back the msgs[], with reply and address 0x10
91 the chip and put the alias back in the pool for later usage
|
| /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.
|
12345678910>>...26