Searched +full:per +full:- +full:device (Results 1 – 25 of 598) sorted by relevance
12345678910>>...24
| /Documentation/admin-guide/cgroup-v1/ |
| D | blkio-controller.rst | 16 level logical devices like device mapper.
22 -----------------------------
33 mount -t cgroup -o blkio none /sys/fs/cgroup/blkio
35 Specify a bandwidth rate on particular device for root group. The format
41 on device having major/minor number 8:16.
92 Enable block device throttling support in block layer.
98 --------------------------------
101 Specifies per cgroup weight. This is default weight of the group
102 on all the devices until and unless overridden by per device rule
106 see Documentation/block/bfq-iosched.rst.
[all …]
|
| D | rdma.rst | 8 1-1. What is RDMA controller?
9 1-2. Why RDMA controller needed?
10 1-3. How is RDMA controller implemented?
16 1-1. What is RDMA controller?
17 -----------------------------
25 1-2. Why RDMA controller needed?
26 --------------------------------
37 1-3. How is RDMA controller implemented?
38 ----------------------------------------
41 resource accounting per cgroup, per device using resource pool structure.
[all …]
|
| /Documentation/usb/ |
| D | dwc3.rst | 11 - Convert interrupt handler to per-ep-thread-irq
13 As it turns out some DWC3-commands ~1ms to complete. Currently we spin
18 - dwc core implements a demultiplexing irq chip for interrupts per
20 to the device. If MSI provides per-endpoint interrupt this dummy
22 - interrupts are requested / allocated on usb_ep_enable() and removed on
25 - dwc3_send_gadget_ep_cmd() will sleep in wait_for_completion_timeout()
27 - the interrupt handler is split into the following pieces:
29 - primary handler of the device
34 - threaded handler of the device
37 - primary handler of the EP-interrupt
[all …]
|
| D | authorization.rst | 5 Copyright (C) 2007 Inaky Perez-Gonzalez <inaky@linux.intel.com> Intel Corporation
7 This feature allows you to control if a USB device can be used (or
8 not) in a system. This feature will allow you to implement a lock-down
11 As of now, when a USB device is connected it is configured and
13 modification, only if root authorizes the device to be configured will
19 Authorize a device to connect::
21 $ echo 1 > /sys/bus/usb/devices/DEVICE/authorized
23 De-authorize a device::
25 $ echo 0 > /sys/bus/usb/devices/DEVICE/authorized
42 ------------------------------
[all …]
|
| /Documentation/hwmon/ |
| D | g762.rst | 5 and performs closed-loop or open-loop control of the fan speed. Two
6 modes - PWM or DC - are supported by the device.
9 http://natisbad.org/NAS/ref/GMT_EDS-762_763-080710-0.2.pdf. sysfs
10 bindings are described in Documentation/hwmon/sysfs-interface.rst.
13 /sys/bus/i2c/drivers/g762/ to control the operation of the device.
18 hardware characteristics of the system (reference clock, pulses per
25 set desired fan speed. This only makes sense in closed-loop
30 the fan to the device.
36 number of pulses per fan revolution. Supported values
44 in closed-loop control mode, if fan RPM value is 25% out
[all …]
|
| /Documentation/timers/ |
| D | highres.rst | 8 https://www.kernel.org/doc/ols/2006/ols2006v1-pages-333-346.pdf
11 http://www.cs.columbia.edu/~nahum/w6998/papers/ols2006-hrtimers-slides.pdf
23 - hrtimer base infrastructure
24 - timeofday and clock source management
25 - clock event management
26 - high resolution timer functionality
27 - dynamic ticks
31 ---------------------------
40 - time ordered enqueueing into a rb-tree
41 - independent of ticks (the processing is based on nanoseconds)
[all …]
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | ti,keystone-rproc.txt | 5 sub-systems that are used to offload some of the processor-intensive tasks or
8 These processor sub-systems usually contain additional sub-modules like L1
13 DSP Device Node:
15 Each DSP Core sub-system is represented as a single DT node, and should also
18 CorePac) to perform the device management of the remote processor and to
22 --------------------
25 - compatible: Should be one of the following,
26 "ti,k2hk-dsp" for DSPs on Keystone 2 66AK2H/K SoCs
27 "ti,k2l-dsp" for DSPs on Keystone 2 66AK2L SoCs
28 "ti,k2e-dsp" for DSPs on Keystone 2 66AK2E SoCs
[all …]
|
| /Documentation/mm/ |
| D | page_frags.rst | 5 A page fragment is an arbitrary-length arbitrary-offset area of memory
12 network stack and network device drivers to provide a backing region of
13 memory for use as either an sk_buff->head, or to be used in the "frags"
22 either a per-cpu limitation, or a per-cpu limitation and forcing interrupts
25 The network stack uses two separate caches per CPU to handle fragment
34 Many network device drivers use a similar methodology for allocating page
41 avoid calling get_page per allocation.
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | richtek,rt5033-charger.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/supply/richtek,rt5033-charger.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jakob Hauser <jahau@rocketmail.com>
13 The battery charger of the multifunction device RT5033 has to be instantiated
14 under sub-node named "charger" using the following format.
18 const: richtek,rt5033-charger
20 monitored-battery:
26 precharge-current-microamp:
[all …]
|
| /Documentation/power/ |
| D | pm_qos_interface.rst | 11 * The per-device PM QoS framework provides the API to manage the
12 per-device latency constraints and PM QoS flags.
65 The infrastructure exposes one device node, /dev/cpu_dma_latency, for the CPU
75 As long as the device node is held open that process has a registered
79 the open device node. Alternatively, it can write a hex string for the value
83 To remove the user mode request for a target value simply close the device
87 2. PM QoS per-device latency and flags framework
90 For each device, there are three lists of PM QoS requests. Two of them are
98 values. One device PM QoS flag is defined currently: PM_QOS_FLAG_NO_POWER_OFF.
106 int dev_pm_qos_add_request(device, handle, type, value):
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-info.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
7 The ``devlink-info`` mechanism enables device drivers to report device
10 The original motivation for the ``devlink-info`` API was twofold:
12 - making it possible to automate device and firmware management in a fleet
13 of machines in a vendor-independent fashion (see also
14 :ref:`Documentation/networking/devlink/devlink-flash.rst <devlink_flash>`);
15 - name the per component FW versions (as opposed to the crowded ethtool
18 ``devlink-info`` supports reporting multiple types of objects. Reporting driver
19 versions is generally discouraged - here, and via any other Linux API.
21 .. list-table:: List of top level info objects
[all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-davinci.txt | 3 This file provides information, what the device node for the
7 - compatible: "ti,davinci-i2c" or "ti,keystone-i2c";
8 - reg : Offset and length of the register set for the device
9 - clocks: I2C functional clock phandle.
10 For 66AK2G this property should be set per binding,
11 Documentation/devicetree/bindings/clock/ti,sci-clk.yaml
13 SoC-specific Required Properties:
17 - power-domains: Should contain a phandle to a PM domain provider node
18 and an args specifier containing the I2C device id
19 value. This property is as per the binding,
[all …]
|
| D | i2c.txt | 1 Generic device tree bindings for I2C busses
5 busses and their child devices in a device tree.
7 Required properties (per bus)
8 -----------------------------
10 - #address-cells - should be <1>. Read more about addresses below.
11 - #size-cells - should be <0>.
12 - compatible - name of I2C bus controller
20 Optional properties (per bus)
21 -----------------------------
26 - clock-frequency
[all …]
|
| /Documentation/filesystems/ |
| D | devpts.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 To retain backwards compatibility the a ptmx device node (aka any node
16 of devpts under the name ``pts`` in the same directory as the ptmx device
19 As an option instead of placing a ``/dev/ptmx`` device node at ``/dev/ptmx``
27 kernel.pty.max = 4096 - global limit
28 kernel.pty.reserve = 1024 - reserved for filesystems mounted from the initial mount namespace
29 kernel.pty.nr - current count of ptys
31 Per-instance limit could be set by adding mount option ``max=<count>``.
36 In kernels older than 3.4 sysctl ``kernel.pty.max`` works as per-instance limit.
|
| D | inotify.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Inotify - A Powerful yet Simple File Change Notification System
13 - Deleted obsoleted interface, just refer to manpages for user interface.
22 Watches are associated with an open inotify device, not an open file.
29 What is the design decision behind using an-fd-per-instance as opposed to
30 an fd-per-watch?
33 An fd-per-watch quickly consumes more file descriptors than are allowed,
35 select()-able. Yes, root can bump the per-process fd limit and yes, users
38 spaces is thus sensible. The current design is what user-space developers
41 thousand times is silly. If we can implement user-space's preferences
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | amd-xgbe.txt | 1 * AMD 10GbE driver (amd-xgbe)
4 - compatible: Should be "amd,xgbe-seattle-v1a"
5 - reg: Address and length of the register sets for the device
6 - MAC registers
7 - PCS registers
8 - SerDes Rx/Tx registers
9 - SerDes integration registers (1/2)
10 - SerDes integration registers (2/2)
11 - interrupts: Should contain the amd-xgbe interrupt(s). The first interrupt
12 listed is required and is the general device interrupt. If the optional
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-integrity.rst | 2 dm-integrity
5 The dm-integrity target emulates a block device that has additional
6 per-sector tags that can be used for storing integrity information.
9 writing the sector and the integrity tag must be atomic - i.e. in case of
12 To guarantee write atomicity, the dm-integrity target uses journal, it
16 The dm-integrity target can be used with the dm-crypt target - in this
17 situation the dm-crypt target creates the integrity data and passes them
18 to the dm-integrity target via bio_integrity_payload attached to the bio.
19 In this mode, the dm-crypt and dm-integrity targets provide authenticated
20 disk encryption - if the attacker modifies the encrypted device, an I/O
[all …]
|
| /Documentation/filesystems/nfs/ |
| D | pnfs.rst | 5 The are several inter-related caches. We have layouts which can
7 Each data server can be referenced by multiple devices. Each device
15 The on-the-wire command LAYOUTGET corresponds to struct
18 segments in nfsi->layout, of type struct pnfs_layout_hdr.
24 Each header is also (when non-empty) put on a list associated with
32 lsegs reference device ids, which are resolved per nfs_client and
33 layout driver type. The device ids are held in a RCU cache (struct
41 deviceid's per filesystem, and multiple filesystems per nfs_client.
67 of these types there is a layout-driver with a common function-vectors
68 table which are called by the nfs-client pnfs-core to implement the
[all …]
|
| /Documentation/translations/it_IT/process/ |
| D | 8.Conclusion.rst | 1 .. include:: ../disclaimer-ita.rst
8 Per maggiori informazioni
16 importante; :ref:`process/submitting-patches.rst <it_submittingpatches>` è
19 kerneldoc; "make htmldocs" o "make pdfdocs" possono essere usati per generare
31 Oltre a ciò, una risorsa valida per gli sviluppatori kernel è:
36 definitivo per le informazioni sui rilasci del kernel.
40 Linux Device Drivers, 3rd Edition (Jonathan Corbet, Alessandro
41 Rubini, and Greg Kroah-Hartman). In linea all'indirizzo
52 La documentazione per git la troverete su:
56 http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | apple,aic.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/apple,aic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Hector Martin <marcan@marcan.st>
19 - Level-triggered hardware IRQs wired to SoC blocks
20 - Single mask bit per IRQ
21 - Per-IRQ affinity setting
22 - Automatic masking on event delivery (auto-ack)
23 - Software triggering (ORed with hw line)
[all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | rotary-encoder.txt | 4 - gpios: a spec for at least two GPIOs to be used, most significant first
7 - linux,axis: the input subsystem axis to map to this rotary encoder.
9 - rotary-encoder,steps: Number of steps in a full turnaround of the
12 - rotary-encoder,relative-axis: register a relative axis rather than an
13 absolute one. Relative axis will only generate +1/-1 events on the input
14 device, hence no steps need to be passed.
15 - rotary-encoder,rollover: Automatic rollover when the rotary value becomes
17 - rotary-encoder,steps-per-period: Number of steps (stable states) per period.
19 1: Full-period mode (default)
20 2: Half-period mode
[all …]
|
| /Documentation/driver-api/ |
| D | mtdnand.rst | 10 The generic NAND driver supports almost all NAND and AG-AND based chips
31 --------------------------
37 - [MTD Interface]
43 - [NAND Interface]
48 - [GENERIC]
53 - [DEFAULT]
65 -------------------------------
71 - [INTERN]
77 - [REPLACEABLE]
86 - [BOARDSPECIFIC]
[all …]
|
| D | men-chameleon-bus.rst | 31 ----------------------
38 -----------------------------------------
44 - Multi-resource MCB devices like the VME Controller or M-Module carrier.
45 - MCB devices that need another MCB device, like SRAM for a DMA Controller's
47 - A per-carrier IRQ domain for carrier devices that have one (or more) IRQs
48 per MCB device like PCIe based carriers with MSI or MSI-X support.
55 - The MEN Chameleon Bus itself,
56 - drivers for MCB Carrier Devices and
57 - the parser for the Chameleon table.
60 -----------------
[all …]
|
| /Documentation/networking/ |
| D | alias.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 IP-Aliasing
7 IP-aliases are an obsolete way to manage multiple IP-addresses/masks
8 per interface. Newer tools such as iproute2 support multiple
9 address/prefixes per interface, but aliases are still supported
24 ~~ -> request alias #0 creation (if not yet exists) for eth0
36 ~~~~~~~~~~ -> will delete alias
39 Alias (re-)configuring
46 Relationship with main device
49 If the base device is shut down the added aliases will be deleted too.
|
| /Documentation/devicetree/bindings/iio/afe/ |
| D | temperature-transducer.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/iio/afe/temperature-transducer.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Liam Beguin <liambeguin@gmail.com>
13 A temperature transducer is a device that converts a thermal quantity
19 When an io-channel measures the output voltage of a temperature analog front
35 -----
37 +---+---+
39 +---+---+ -----
[all …]
|
12345678910>>...24