Searched full:resources (Results 1 – 25 of 282) sorted by relevance
12345678910>>...12
| /Documentation/admin-guide/cgroup-v1/ |
| D | rdma.rst | 19 RDMA controller allows user to limit RDMA/IB specific resources that a given
22 RDMA controller defines two resources which can be limited for processes of a
29 specific resources such as AH, CQ, QP, MR etc. Due to which other applications
31 rdma resources. This can lead to service unavailability.
35 resources can be accounted.
40 RDMA cgroup allows limit configuration of resources. Rdma cgroup maintains
42 Each such resource pool is limited up to 64 resources in given resource pool
51 Since RDMA resources can be allocated from any process and can be freed by any
52 of the child processes which shares the address space, rdma resources are
56 rdma resources. Linking resources around css also ensures that cgroups can be
[all …]
|
| /Documentation/PCI/ |
| D | acpi-info.rst | 30 resources conflict with them.
79 programming model for them other than "don't use these resources for
111 ACPI Namespace that report the hardware resources the device could
112 occupy [_PRS], an object that reports the resources that are currently
113 used by the device [_CRS], and objects for configuring those resources
118 OSPM uses device configuration objects to configure hardware resources
121 relationship between shared resources, and methods for configuring
122 hardware resources.
127 Play system determines what resources the device should consume and
128 sets those resources by calling the device’s _SRS control method.
[all …]
|
| /Documentation/gpu/ |
| D | vgaarbiter.rst | 18 control bus resources. Therefore an arbitration scheme outside of the X server
19 is needed to control the sharing of these resources. This document introduces
126 These functions below acquire VGA resources for the given card and mark those
127 resources as locked. If the resources requested are "normal" (and not legacy)
128 resources, the arbiter will first check whether the card is doing legacy
132 forwarding on P2P bridges if necessary, so that the requested resources can
133 be used. Then, the card is marked as locking these resources and the IO and/or
136 if some conflicting card is already locking one of the required resources (or
138 VGA memory and IO afaik). If the card already owns the resources, the function
147 resources, both will succeed (lock). If devices are in different buses and
[all …]
|
| /Documentation/filesystems/ |
| D | sysfs-pci.txt | 1 Accessing PCI device resources through sysfs
4 sysfs, usually mounted at /sys, provides access to PCI resources on platforms
66 don't support mmapping of certain resources, so be sure to check the return
68 resources, which also provide read/write access.
91 Accessing legacy resources through sysfs
94 Legacy I/O port and ISA memory resources are also provided in sysfs if the
124 Platforms which support write-combining maps of PCI resources must define
126 write-combining is permitted. Platforms which support maps of I/O resources
129 Legacy resources are protected by the HAVE_PCI_LEGACY define. Platforms
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-power_state | 14 If the device node uses shared ACPI power resources, this state
15 determines a list of power resources required not to be turned
16 off. However, some power resources needed by the device node in
|
| D | sysfs-devices-real_power_state | 7 power management methods and use ACPI power resources for power
13 resources. Its possible values, "D0", "D1", "D2", "D3hot", and
20 resources used by the device node are only ON because of some
|
| D | sysfs-devices-power_resources_D0 | 7 use ACPI power resources for power management.
10 representing ACPI power resources that need to be turned on for
|
| D | sysfs-devices-power_resources_wakeup | 7 require ACPI power resources for wakeup signaling.
10 representing ACPI power resources that need to be turned on for
|
| D | sysfs-devices-power_resources_D1 | 7 use ACPI power resources for power management and support ACPI
11 representing ACPI power resources that need to be turned on for
|
| D | sysfs-devices-power_resources_D2 | 7 use ACPI power resources for power management and support ACPI
11 representing ACPI power resources that need to be turned on for
|
| D | sysfs-devices-power_resources_D3hot | 7 use ACPI power resources for power management and support ACPI
11 representing ACPI power resources that need to be turned on for
|
| /Documentation/admin-guide/ |
| D | pnp.rst | 12 Plug and Play provides a means of detecting and setting resources for legacy or
28 - resources - displays currently allocated resources and allows resource changes
35 # echo "auto" > resources
44 # echo "manual <depnum> <mode>" > resources
56 # echo "disable" > resources
72 # cat resources
93 # echo "auto" > resources
97 # cat resources
171 - the ability to set resources is optional but preferred.
235 the resources, such as the parport_pc driver.
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smd-rpm.txt | 5 for state of the system resources, such as clocks, regulators and bus
14 The RPM exposes resources to its subnodes. The rpm_requests node must be
16 resources.
|
| D | qcom,aoss-qmp.txt | 10 The AOSS side channel exposes control over a set of resources, used to control
11 a set of debug related clocks and to affect the low power state of resources
12 related to the secondary subsystems. These resources are exposed as a set of
|
| /Documentation/arm/samsung-s3c24xx/ |
| D | eb2410itx.rst | 30 - Resources Page http://www.simtec.co.uk/products/EB2410ITX/resources.html
34 - Bootloader info http://www.simtec.co.uk/products/SWABLE/resources.html
|
| /Documentation/firmware-guide/acpi/ |
| D | gpio-properties.rst | 45 The device that has _CRS containing GpioIo()/GpioInt() resources,
127 with GpioIo()/GpioInt() resources and device drivers still need to work with
133 listed by the GpioIo()/GpioInt() resources returned by _CRS. In other words,
134 the driver is supposed to know what to use the GpioIo()/GpioInt() resources for
137 mapping between those names and the ACPI GPIO resources corresponding to them.
224 defined device properties and will prevent to getting any GPIO resources
227 Case 2 explicitly tells GPIO core to look for resources in _CRS.
231 present in the driver, will return different resources. That's why a
|
| /Documentation/infiniband/ |
| D | user_verbs.rst | 36 Since creation and destruction of all IB resources is done by
38 of which resources are attached to a given userspace context. The
45 prevent one process from touching another process's resources.
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | data-structure-v9.rst | 11 A node has a number of DRBD resources. Each such resource has a number of
30 In this table, horizontally, devices can be accessed from resources by their
36 All resources are in the drbd_resources double-linked list. In addition, all
|
| /Documentation/powerpc/ |
| D | elfnote.rst | 27 In an ultravisor-enabled system, some machine resources are now controlled
30 trying to access ultravisor resources. For instance, it may crash in early
|
| /Documentation/userspace-api/ |
| D | unshare.rst | 30 special resources and mechanisms to maintain these "threads". The Linux
33 resources and thus they can achieve legacy "threads" behavior without
37 outside the confinement of all-or-nothing shared resources of legacy
39 call, applications can selectively choose which resources to share
43 allows threads to selectively 'unshare' any resources that were being
48 shared resources without creating a new process. unshare() is a natural
57 resources is not possible. Since namespaces are shared by default
83 client requests by creating processes that share resources such as
120 incremental unsharing of those resources on an as needed basis.
|
| /Documentation/driver-api/driver-model/ |
| D | devres.rst | 41 So, many low level drivers end up leaking resources on driver detach
43 would leak resources or even cause oops when failure occurs. iomap
57 Managed interface is created for resources commonly used by device
101 detached. If most resources are acquired using managed interface, a
139 like allocating memory, have failed. Managed resources pertains to the
140 freeing of these resources *only* - all other checks needed are still
151 resources on failure. For example::
|
| /Documentation/devicetree/bindings/net/ |
| D | cortina,gemini-ethernet.txt | 19 They are not independent of each other since they share resources
23 - port0: contains the resources for ethernet port 0
24 - port1: contains the resources for ethernet port 1
|
| /Documentation/networking/device_drivers/freescale/dpaa2/ |
| D | ethernet-driver.rst | 21 representing network interfaces; instead, several separate hardware resources
29 All hardware resources are allocated and configured through the Management
30 Complex (MC) portals. MC abstracts most of these resources as DPAA2 objects
32 hardware resources, like queues, do not have a corresponding MC object and
33 are treated as internal resources of other objects.
70 hardware resources.
158 options and associated hardware resources.
|
| /Documentation/livepatch/ |
| D | callbacks.rst | 49 resources
54 used to cleanup pre-patch callback resources
65 configures resources with an unpatch handler tears down and releases
66 those same resources.
|
| /Documentation/driver-api/ |
| D | console.rst | 128 2. All resources allocated during con->con_init() must be released in
131 3. All resources allocated in con->con_startup() must be released when the
134 driver to check when it's legal to release these resources. Calling
136 false(), then it's safe to release the resources. This balance has to be
|
12345678910>>...12