Searched full:how (Results 1 – 25 of 870) sorted by relevance
12345678910>>...35
/Documentation/ABI/testing/ |
D | sysfs-kernel-mm-ksm | 19 full_scans: how many times all mergeable areas have been 22 pages_shared: how many shared pages are being used. 24 pages_sharing: how many more sites are sharing them i.e. how 27 pages_to_scan: how many present pages to scan before ksmd goes 30 pages_unshared: how many pages unique but repeatedly checked 33 pages_volatile: how many pages changing too fast to be placed 41 sleep_millisecs: how many milliseconds ksm should sleep between
|
D | sysfs-kernel-slab | 19 The aliases file is read-only and specifies how many caches 48 The alloc_fastpath file shows how many objects have been 59 The alloc_from_partial file shows how many times a cpu slab has 71 The alloc_refill file shows how many times the per-cpu freelist 82 The alloc_slab file is shows how many times a new slab had to 93 The alloc_slowpath file shows how many objects have been 115 The cpu_slabs file is read-only and displays how many cpu slabs 124 The file cpuslab_flush shows how many times a cache's cpu slabs 147 The deactivate_empty file shows how many times an empty cpu slab 157 The deactivate_full file shows how many times a full cpu slab [all …]
|
D | sysfs-kernel-ion | 17 The total_heaps_kb file is read-only and specifies how much 26 The total_pools_kb file is read-only and specifies how much
|
D | sysfs-class-led-trigger-oneshot | 6 Specifies for how many milliseconds the LED has to stay at 15 Specifies for how many milliseconds the LED has to stay at
|
/Documentation/admin-guide/mm/ |
D | ksm.rst | 82 how many pages to scan before ksmd goes to sleep 88 how many milliseconds ksmd should sleep before next scan 101 sharing of setting 1 (default). You may wish to compare how 153 specifies how frequently KSM checks the metadata of the pages 163 how many shared pages are being used 165 how many more sites are sharing them i.e. how much saved 167 how many pages unique but repeatedly checked for merging 169 how many pages changing too fast to be placed in a tree 171 how many times all mergeable areas have been scanned
|
/Documentation/userspace-api/media/v4l/ |
D | vidioc-subdev-enum-mbus-code.rst | 97 See :ref:`v4l2-mbus-format` on how to do this. 104 See :ref:`v4l2-mbus-format` on how to do this. 111 See :ref:`v4l2-mbus-format` on how to do this. 118 See :ref:`v4l2-mbus-format` on how to do this. 125 See :ref:`v4l2-mbus-format` on how to do this.
|
/Documentation/x86/x86_64/ |
D | machinecheck.rst | 15 mcelog knows how to decode them. 40 How often to poll for corrected machine check errors, in seconds 56 how hard the kernel tries to recover even at some risk of 75 How long to wait for the other CPUs to machine check too on a
|
/Documentation/filesystems/nfs/ |
D | knfsd-stats.rst | 49 Counts how many NFS packets have arrived. More precisely, this 59 of how much CPU load is being placed on the sunrpc server layer 63 Counts how many times an NFS transport is enqueued to wait for 79 Counts how many times an idle nfsd thread is woken to try to 88 Counts how many times an nfsd thread triggered an idle timeout,
|
/Documentation/firmware-guide/acpi/ |
D | extcon-intel-int3496.rst | 9 This ACPI device describes how the OS can read the id-pin of the devices' 10 USB-otg port, as well as how it optionally can enable Vbus output on the 11 otg port and how it can optionally control the muxing of the data pins
|
D | osi.rst | 16 This document explains how and why the BIOS and Linux should use these methods. 17 It also explains how and why they are widely misused. 19 How to use _OSI 43 for Linux to deal with how Linux is different from Windows. 65 That was easy. Read on, to find out how to do it wrong. 107 eg. _OSI("3.0 Thermal Model") would return TRUE if the OS knows how
|
/Documentation/process/ |
D | howto.rst | 7 instructions on how to become a Linux kernel developer and how to learn 20 So, you want to learn how to become a Linux kernel developer? Or you 24 and hints on how to work with the community. It will also try to 49 Please remember that you are trying to learn how to work with the 64 rules and how to use `SPDX <https://spdx.org/>`_ identifiers in source code are 79 invaluable for learning how to interact with the kernel community. When 81 documentation files are also added which explain how to use the feature. 109 These files describe in explicit detail how to successfully create 120 Other excellent descriptions of how to create patches properly are: 147 This document describes how Linux kernel maintainers operate and the [all …]
|
D | 7.AdvancedTopics.rst | 6 At this point, hopefully, you have a handle on how the development process 27 teach the reader how to use git; that would be sufficient material for a 28 long document in its own right. Instead, the focus here will be on how git 39 understanding of how git works before trying to use it to make patches 111 useful in such situations; it remembers how merge conflicts were resolved 156 learn how to program in the kernel environment than by looking at code 166 comments as questions rather than criticisms. Asking "how does the lock
|
/Documentation/maintainer/ |
D | maintainer-entry-profile.rst | 17 Provide an introduction to how the subsystem operates. While MAINTAINERS 85 One of the largest sources of contributor angst is how soon to ping 87 addition to specifying how long to wait before a resubmission this 90 list how review works for this code area and methods to get feedback
|
/Documentation/power/ |
D | swsusp-dmcrypt.rst | 2 How to use dm-crypt and swsusp together 10 You know how dm-crypt works. If not, visit the following web page: 13 You did read Documentation/admin-guide/initrd.rst and know how an initrd works. 14 You know how to create or how to modify an initrd.
|
/Documentation/usb/ |
D | chipidea.rst | 5 1. How to test OTG FSM(HNP and SRP) 8 To show how to demo OTG HNP and SRP functions via sys input files 11 1.1 How to enable OTG FSM 105 2. How to enable USB as system wakeup source 107 Below is the example for how to enable USB as system wakeup source
|
/Documentation/driver-api/gpio/ |
D | intro.rst | 9 The documents in this directory give detailed instructions on how to access 10 GPIOs in drivers, and how to write a driver for a device that provides GPIOs 44 firmware knowing how they're used). 49 options about how that value is driven, so that for example only one 122 example, that's how I2C clocks are stretched: a slave that needs a slower clock
|
/Documentation/driver-api/dmaengine/ |
D | index.rst | 22 This book is a guide to device driver writers on how to use the Slave-DMA 33 This book introduces how to test DMA drivers using dmatest module.
|
/Documentation/litmus-tests/ |
D | README | 7 For more information about how to "run" a litmus test or how to generate
|
/Documentation/fb/ |
D | deferred_io.rst | 7 IO. The following example may be a useful explanation of how one such setup 43 How to use it: (for applications) 47 How to use it: (for fbdev drivers)
|
/Documentation/devicetree/bindings/input/ |
D | ti,nspire-keypad.txt | 11 - scan-interval: How often to scan in us. Based on a APB speed of 33MHz, the 14 - row-delay: How long to wait before scanning each row.
|
/Documentation/ |
D | index.rst | 25 (GPLv2), how to properly mark the license of individual files in the source 68 These manuals contain overall information about how to develop the kernel. 71 knowing how things are done will make the process of getting your changes 90 These books get into the details of how specific kernel subsystems work
|
/Documentation/core-api/ |
D | symbol-namespaces.rst | 5 The following document describes how to use Symbol Namespaces to structure the 12 === 2 How to define Symbol Namespaces 15 === 3 How to use Symbols exported in Namespaces 31 2. How to define Symbol Namespaces 87 3. How to use Symbols exported in Namespaces
|
/Documentation/devicetree/bindings/dma/ |
D | qcom_hidma_mgmt.txt | 13 Other parameters here determine how much of the system bus this HIDMA 31 - max-write-transactions: This value is how many times a write burst is 34 - max-read-transactions: This value is how many times a read burst is
|
/Documentation/ABI/ |
D | README | 32 layout of the files below for details on how to do this.) 50 Description: Long description of the interface and how to use it. 69 How things move between levels:
|
/Documentation/filesystems/ |
D | index.rst | 8 comprehensive information on how the Linux virtual filesystem (VFS) layer 15 See these manuals for documentation about the VFS layer itself and how its
|
12345678910>>...35