Searched full:scheme (Results 1 – 25 of 151) sorted by relevance
1234567
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-light-isl29018 | 9 Scheme 0, makes full n (4, 8, 12, 16) bits (unsigned) proximity
10 detection. The range of Scheme 0 proximity count is from 0 to
11 2^n. Logic 1 of this bit, Scheme 1, makes n-1 (3, 7, 11, 15)
13 range of Scheme 1 proximity count is from -2^(n-1) to 2^(n-1).
15 Scheme 0 has wider dynamic range, Scheme 1 proximity detection
|
| D | sysfs-kernel-mm-damon | 31 contents of 'tried_regions' directory of every scheme directory
145 directories for controlling each DAMON-based operation scheme
152 of the scheme.
158 size of the scheme's target regions in bytes.
164 size of the scheme's target regions in bytes.
170 'nr_accesses' of the scheme's target regions.
176 'nr_accesses' of the scheme's target regions.
182 'age' of the scheme's target regions.
188 'age' of the scheme's target regions.
194 quota of the scheme in milliseconds.
[all …]
|
| /Documentation/admin-guide/mm/damon/ |
| D | usage.rst | 129 for each DAMON-based operation scheme of the kdamond. For details of the
133 DAMON-based operation scheme action tried regions directory for each
134 DAMON-based operation scheme of the kdamond. Writing
138 operating scheme action tried regions directory for each DAMON-based operation
139 scheme of the kdamond. For details of the DAMON-based operation scheme action
267 to ``N-1``. Each directory represents each DAMON-based operation scheme.
272 In each scheme directory, five directories (``access_pattern``, ``quotas``,
276 The ``action`` file is for setting and getting the scheme's :ref:`action
304 <damon_design_damos_access_pattern>` of the given DAMON-based operation scheme.
308 exist. You can set and get the access pattern for the given scheme by writing
[all …]
|
| /Documentation/mm/damon/ |
| D | design.rst | 170 This scheme, however, cannot preserve the quality of the output if the
294 regions that the scheme is having an interest in.
304 region having the access pattern of interest is found, applying the scheme's
328 scheme action. In contrast, the colder regions would be deprioritized for huge
329 page collapse scheme action. Hence, the prioritization mechanisms for each
350 memory is guaranteed, running a scheme for proactive reclamation would only
358 high watermark or below the low watermark, the scheme is deactivated. If the
359 metric becomes below the mid watermark but above the low watermark, the scheme
379 number of filters for each scheme. Each filter specifies the type of target
397 it is not counted as the scheme has tried to the region. In contrast, if a
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | ifork.rst | 36 Note that with this block mapping scheme, it is necessary to fill out a
38 led to the creation of the extent mapping scheme, discussed below.
40 Notice also that a file using this mapping scheme cannot be placed
47 tree. Under the old scheme, allocating a contiguous run of 1,000 blocks
|
| D | allocators.rst | 25 Under this scheme, when a file needs more blocks to absorb file writes,
51 this scheme evens out the loading on the block groups, though the author
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | qnap-poweroff.txt | 8 Synology NAS devices use a similar scheme, but a different baud rate,
|
| /Documentation/scsi/ |
| D | aha152x.rst | 126 The BIOS uses a cylinder/head/sector addressing scheme (C/H/S)
127 scheme instead. DOS expects a BIOS or driver that understands this
135 geometry just to be able to support that addressing scheme. The geometry
145 Moreover there are certain limitations to the C/H/S addressing scheme,
|
| /Documentation/translations/zh_CN/admin-guide/mm/damon/ |
| D | usage.rst | 427 用户可以通过读取和写入 ``scheme`` debugfs文件来获得和设置这些方案。读取该文件还可以显示每个
514 # scheme="4096 8192 0 5 10 20 2" # target access pattern and action
515 # scheme+=" 10 $((1024*1024*1024)) 1000" # quotas
516 # scheme+=" 0 0 100" # prioritization weights
517 # scheme+=" 1 5000000 600 500 300" # watermarks
518 # echo "$scheme" > schemes
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 6 Locking scheme used for directory operations is based on two
66 If no directory is its own ancestor, the scheme above is deadlock-free.
139 While this locking scheme works for arbitrary DAGs, it relies on
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | qcom,smem-part.yaml | 14 Memory (SMEM) based partition table scheme. The maximum partitions supported
|
| /Documentation/devicetree/bindings/sound/ |
| D | ti,tas5086.txt | 25 sequence, otherwise the default Low-Z scheme is used.
|
| /Documentation/admin-guide/perf/ |
| D | qcom_l2_pmu.rst | 26 which is outside the above scheme.
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | ti,pru-consumer.yaml | 49 This selects the internal muxing scheme for the PRU instance. Values
|
| /Documentation/userspace-api/media/drivers/ |
| D | aspeed-video.rst | 16 Support 2-pass (high quality) video compression scheme (Patent pending by
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | qcom-ipcc.yaml | 15 addressing scheme called protocol, client and signal. For example, consider an
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,rpm-master-stats.yaml | 26 This scheme has been used on various SoCs in the 2013-2023 era, with some
|
| /Documentation/devicetree/bindings/firmware/ |
| D | nvidia,tegra186-bpmp.yaml | 53 such services. Put another way, the numbering scheme for I2C buses is
54 distinct from the numbering scheme for any other service the BPMP may
|
| /Documentation/devicetree/bindings/opp/ |
| D | operating-points-v2-ti-cpu.yaml | 19 the hardware description for the scheme mentioned above.
|
| /Documentation/pcmcia/ |
| D | locking.rst | 5 This file explains the locking and exclusion scheme used in the PCCARD
|
| /Documentation/devicetree/bindings/clock/ |
| D | imx7ulp-scg-clock.yaml | 17 The clocking scheme provides clear separation between M4 domain
|
| /Documentation/hid/ |
| D | hidreport-parsing.rst | 42 Moving now to the second two bytes, and following the same scheme,
|
| /Documentation/devicetree/bindings/display/ |
| D | dsi-controller.yaml | 59 from 0 to 3, as DSI uses a 2-bit addressing scheme. Some DSI
|
| /Documentation/leds/ |
| D | leds-blinkm.rst | 21 The registration follows the scheme::
|
| /Documentation/iio/ |
| D | ep93xx_adc.rst | 15 Numbering scheme for channels 0..4 is defined in EP9301 and EP9302 datasheets.
|
1234567