Searched full:scan (Results 1 – 25 of 138) sorted by relevance
123456
| /Documentation/scheduler/ |
| D | sched-debug.rst | 24 memory node local to where the task is running. Every "scan delay" the task
25 scans the next "scan size" number of pages in its address space. When the
28 In combination, the "scan delay" and "scan size" determine the scan rate.
29 When "scan delay" decreases, the scan rate increases. The scan delay and
30 hence the scan rate of every task is adaptive and depends on historical
31 behaviour. If pages are properly placed then the scan delay increases,
32 otherwise the scan delay decreases. The "scan size" is not adaptive but
33 the higher the "scan size", the higher the scan rate.
35 Higher scan rates incur higher system overhead as page faults must be
36 trapped and potentially data must be migrated. However, the higher the scan
[all …]
|
| /Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 5 ACPI Scan Handlers
26 The core ACPI namespace scanning code in drivers/acpi/scan.c carries out basic
39 called ACPI scan handlers represented by the following structure::
49 take care of, list_node is the hook to the global list of ACPI scan handlers
56 to match a scan handler against each of them using the ids arrays of the
57 available scan handlers. If a matching scan handler is found, its .attach()
62 The device node's handler field is then populated with the address of the scan
66 interesting to the given scan handler and may be matched against the next scan
68 the namespace scan should be terminated due to a serious error. The error code
72 callbacks from the scan handlers of all device nodes in the given namespace
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | ksm.rst | 80 how many pages to scan before ksmd goes to sleep
84 been set to scan-time.
89 how many milliseconds ksmd should sleep before next scan
158 scan. It's a noop if not a single KSM page hit the
162 Historically KSM checked every candidate page for each scan. It did
163 not take into account historic information. When smart scan is
172 supported: none and scan-time. The default is none. By setting
173 ``advisor_mode`` to scan-time, the scan time advisor is enabled.
174 The section about ``advisor`` explains in detail how the scan time
182 specifies the target scan time in seconds to scan all the candidate
[all …]
|
| D | shrinker_debugfs.rst | 13 Each shrinker directory contains **count** and **scan** files, which allow to
46 count scan
106 4. *Scan objects*
110 <cgroup inode id> <numa id> <number of objects to scan>
126 $ echo "55 0 200" > scan
|
| /Documentation/dev-tools/ |
| D | kmemleak.rst | 26 To trigger an intermediate memory scan::
28 # echo scan > /sys/kernel/debug/kmemleak
50 - scan=on
52 - scan=off
54 - scan=<secs>
57 - scan
58 trigger a memory scan
101 2. scan the memory starting with the data section and stacks, checking
105 3. scan the gray objects for matching addresses (some white objects
124 /sys/kernel/debug/kmemleak output. By issuing a 'scan' after a 'clear'
[all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | lpc32xx-key.txt | 1 NXP LPC32xx Key Scan Interface
13 - nxp,scan-delay-ms: Repeated scan period in ms
32 nxp,scan-delay-ms = <34>;
|
| D | gpio-matrix-keypad.txt | 25 - col-scan-delay-us: delay, measured in microseconds, that is needed
26 before we can scan keypad after activating column gpio
27 - drive-inactive-cols: drive inactive columns during scan,
34 col-scan-delay-us = <2>;
|
| D | ti,nspire-keypad.yaml | 30 scan-interval:
32 description: How often to scan in us. Based on a APB speed of 33MHz, the
47 - scan-interval
63 scan-interval = <1000>;
|
| D | gpio-mouse.yaml | 20 scan-interval-ms:
46 - scan-interval-ms
60 scan-interval-ms = <50>;
|
| D | qcom,pm8921-keypad.yaml | 45 scan-delay:
85 scan-delay = <32>;
|
| /Documentation/fb/ |
| D | viafb.modes | 14 # Scan Frequency 31.469 kHz 59.94 Hz
39 # Scan Frequency 37.500 kHz 75.00 Hz
60 # Scan Frequency 43.269 kHz 85.00 Hz
81 # Scan Frequency 50.900 kHz 100.00 Hz
102 # Scan Frequency 61.800 kHz 120.00 Hz
123 # Scan Frequency 30.000 kHz 60.241 Hz
144 # Scan Frequency 29.892 kHz 60.00 Hz
165 # Scan Frequency 35.820 kHz 60.00 Hz
186 # Scan Frequency 37.879 kHz 60.32 Hz
208 # Scan Frequency 46.875 kHz 75.00 Hz
[all …]
|
| /Documentation/translations/zh_CN/dev-tools/ |
| D | kmemleak.rst | 32 # echo scan > /sys/kernel/debug/kmemleak
54 * scan=on
56 * scan=off
58 * scan=<secs>;
61 * scan
109 /sys/kernel/debug/kmemleak 输出的所有的未引用对象。在执行 'clear' 后执行 'scan'
116 # echo scan > /sys/kernel/debug/kmemleak
206 # echo scan > /sys/kernel/debug/kmemleak
|
| /Documentation/driver-api/media/ |
| D | rc-core.rst | 12 Every time a key is pressed on a remote controller, a scan code is produced.
43 scan code, being 8 bits for address (usually it is a fixed number for a
57 microcontroller that decode the *PULSE/SPACE* sequence and return scan
70 corresponding scan code. The protocols supported by the RC core are
73 When the RC code receives a scan code (either directly, by a driver
|
| /Documentation/admin-guide/media/ |
| D | faq.rst | 48 for example the ``dvbv5-scan`` tool. You can find more information
51 https://www.linuxtv.org/wiki/index.php/Dvbv5-scan
54 blind scan, trying hard to find all possible channels, but
60 to scan for services. So, you don't need to use an external
70 https://git.linuxtv.org/dtv-scan-tables.git
74 Kaffeine has some blind scan support for some terrestrial standards.
75 It also relies on DTV scan tables, although it contains a copy
88 list with a tool like ``dvbv5-scan``.
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 58 • Scan Value
60 • Inverted Scan Value
62 • Scan Range
69 • Inverted Scan Range
92 • Scan Value
94 • Inverted Scan Value
96 • Scan Range
98 • Inverted Scan Range
150 0x02 Scan Value
151 0x12 Inverted Scan Value
[all …]
|
| /Documentation/iio/ |
| D | iio_devbuf.rst | 34 be written last, after length and selection of scan elements. Writing a non-zero
41 Read / Write positive integer attribute specifying the maximum number of scan
62 Scan elements
66 a scan element. The scan elements attributes are presented below.
84 Read-only attribute containing the description of the scan element data storage
111 will have the following scan element type for each axis:
|
| /Documentation/translations/zh_CN/scheduler/ |
| D | sched-debug.rst | 29 迁移到任务正在运行的本地内存结点，此时需解映射页面。每个“扫描延迟”（scan delay）
30 时间之后，任务扫描其地址空间中下一批“扫描大小”（scan size）个页面。若抵达
|
| /Documentation/devicetree/bindings/fsi/ |
| D | fsi-controller.yaml | 33 no-scan-on-init:
36 The FSI controller cannot scan the bus during initialization.
|
| /Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 132 'rio-scan.scan' for existing basic enumeration/discovery method.
151 user space. After an enumeration/discovery module is loaded, a network scan
159 When a network scan process is started it calls an enumeration or discovery
207 command line parameter "rio-scan.scan=1".
229 creates the sysfs write-only attribute file '/sys/bus/rapidio/scan'. To initiate
237 write '-1' (or RIO_MPORT_ANY) into the scan attribute file.
248 The method's single parameter "scan" allows to trigger the enumeration/discovery
340 # Load RapidIO switch drivers just before rio-scan enumerator module is loaded
341 softdep rio-scan pre: idt_gen2 idtcps tsi57x
|
| /Documentation/driver-api/iio/ |
| D | buffers.rst | 29 called a scan element. The important bits configuring scan elements are
38 * :file:`type`, description of the scan element data storage within the buffer
65 will have the following scan element type for each axis::
|
| /Documentation/driver-api/media/drivers/ |
| D | vidtv.rst | 346 Using dvb-scan
349 In order to tune into a channel and read the PSI tables, we can use dvb-scan.
351 For this, one should provide a configuration file known as a 'scan file',
366 in the scan file. Just specifying 'FREQUENCY' and 'DELIVERY_SYSTEM'
370 You can browse scan tables online here: `dvb-scan-tables
371 <https://git.linuxtv.org/dtv-scan-tables.git>`_.
375 $ dvbv5-scan channel.conf
376 dvbv5-scan ~/vidtv.conf
385 For more information on dvb-scan, check its documentation online here:
386 `dvb-scan Documentation <https://www.linuxtv.org/wiki/index.php/Dvbscan>`_.
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | sharp,ls037v7dw01.yaml | 11 between QVGA and VGA mode and the scan direction. As these pins can be also
38 scan direction. As these pins can be also configured
|
| /Documentation/filesystems/xfs/ |
| D | xfs-online-fsck-design.rst | 110 …kernel.org/pub/scm/linux/kernel/git/djwong/xfsprogs-dev.git/log/?h=scrub-media-scan-service>`_, and
157 This may expose them to substantial billing costs when a linear media scan
205 entire system, the scan can still be done in the background while other file
217 Because it is necessary for online fsck to lock and scan live metadata objects,
309 6. If the caller asks for a media scan, read all allocated and written data
331 released and the positive scan results are returned to userspace.
333 this, resources are released and the negative scan results are returned to
340 If the repair fails, the scan results from the first step are returned to
439 Repairs, however, require a full scan of primary metadata, which can take a
449 The next step is to release all locks and start the filesystem scan.
[all …]
|
| /Documentation/admin-guide/ |
| D | svga.rst | 21 enter ``scan`` on the video mode prompt, pick the mode you want to use,
66 Enter mode number or ``scan``: <flashing-cursor-here>
95 is able to do more), you can enter "scan" instead of item number / mode ID. The
104 modes are not listed at all and the modes revealed by ``scan`` are shown before
119 have used the ``scan`` feature).
204 stable, explicit mode numbering allowed, "scan" implemented etc.
237 - Better recognition of text modes during mode scan.
244 - Direct testing of SVGA adapters turned off by default, ``scan``
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-intel-ifs | 2 intel_ifs_0 -> Scan Test
49 /lib/firmware/intel/ifs_<N>/ff-mm-ss-02x.scan
|
123456