Searched full:resource (Results 1 – 25 of 370) sorted by relevance
12345678910>>...15
| /Documentation/admin-guide/cgroup-v1/ |
| D | rdma.rst | 33 Therefore RDMA controller is needed through which resource consumption
41 resource accounting per cgroup, per device using resource pool structure.
42 Each such resource pool is limited up to 64 resources in given resource pool
45 This resource pool object is linked to the cgroup css. Typically there
46 are 0 to 4 resource pool instances per cgroup, per device in most use cases.
54 to other cgroup without major complexity of transferring resource ownership;
60 Whenever RDMA resource charging occurs, owner rdma cgroup is returned to
61 the caller. Same rdma cgroup should be passed while uncharging the resource.
62 This also allows process migrated with active RDMA resource to charge
63 to new owner cgroup for new resource. It also allows to uncharge resource of
[all …]
|
| D | pids.rst | 12 place, PIDs are a fundamental resource. As such, PID exhaustion must be
13 preventable in the scope of a cgroup hierarchy by allowing resource limiting of
65 sh: fork: Resource temporary unavailable
80 sh: fork: Resource temporary unavailable
89 sh: fork: Resource temporary unavailable
92 sh: fork: Resource temporary unavailable
|
| /Documentation/networking/devlink/ |
| D | devlink-resource.rst | 4 Devlink Resource
9 resource, as well as how much of the given resource is currently
18 Resource Ids
21 Each resource is represented by an id, and contains information about its
22 current size and related sub resources. To access a sub resource, you
23 specify the path of the resource. For example ``/IPv4/fib`` is the id for
24 the ``fib`` sub-resource under the ``IPv4`` resource.
47 $devlink resource show pci/0000:03:00.0
55 Some resource's size can be changed. Examples:
59 $devlink resource set pci/0000:03:00.0 path /kvd/hash_single size 73088
[all …]
|
| D | netdevsim.rst | 53 $ devlink resource set netdevsim/netdevsim0 path /IPv4/fib size 96
54 $ devlink resource set netdevsim/netdevsim0 path /IPv4/fib-rules size 16
55 $ devlink resource set netdevsim/netdevsim0 path /IPv6/fib size 64
56 $ devlink resource set netdevsim/netdevsim0 path /IPv6/fib-rules size 16
57 $ devlink resource set netdevsim/netdevsim0 path /nexthops size 16
|
| /Documentation/devicetree/bindings/edac/ |
| D | apm-xgene-edac.txt | 15 - regmap-csw : Regmap of the CPU switch fabric (CSW) resource.
16 - regmap-mcba : Regmap of the MCB-A (memory bridge) resource.
17 - regmap-mcbb : Regmap of the MCB-B (memory bridge) resource.
18 - regmap-efuse : Regmap of the PMD efuse resource.
19 - regmap-rb : Regmap of the register bus resource. This property
23 - reg : First resource shall be the CPU bus (PCP) resource.
29 - reg : First resource shall be the memory controller unit
30 (MCU) resource.
36 - reg : First resource shall be the PMD resource.
42 - reg : First resource shall be the L3 EDAC resource.
[all …]
|
| /Documentation/devicetree/bindings/perf/ |
| D | apm-xgene-pmu.txt | 16 - regmap-csw : Regmap of the CPU switch fabric (CSW) resource.
17 - regmap-mcba : Regmap of the MCB-A (memory bridge) resource.
18 - regmap-mcbb : Regmap of the MCB-B (memory bridge) resource.
19 - reg : First resource shall be the CPU bus PMU resource.
24 - reg : First resource shall be the L3C PMU resource.
28 - reg : First resource shall be the IOB PMU resource.
32 - reg : First resource shall be the MCB PMU resource.
37 - reg : First resource shall be the MC PMU resource.
|
| /Documentation/devicetree/bindings/ata/ |
| D | apm-xgene.txt | 9 - reg : First memory resource shall be the AHCI memory
10 resource.
11 Second memory resource shall be the host controller
12 core memory resource.
13 Third memory resource shall be the host controller
14 diagnostic memory resource.
15 4th memory resource shall be the host controller
16 AXI memory resource.
17 5th optional memory resource shall be the host
18 controller MUX memory resource if required.
|
| /Documentation/devicetree/bindings/firmware/ |
| D | gunyah-hypervisor.yaml | 15 of the message queues used to communicate with the Gunyah Resource Manager.
16 …See also: https://github.com/quic/gunyah-resource-manager/blob/develop/src/vm_creation/dto_constru…
32 "^gunyah-resource-mgr(@.*)?":
35 Resource Manager node which is required to communicate to Resource
40 const: gunyah-resource-manager
75 gunyah-resource-mgr@0 {
76 compatible = "gunyah-resource-manager";
|
| /Documentation/staging/ |
| D | remoteproc.rst | 247 also include a special section which we call "the resource table".
249 The resource table contains system resources that the remote processor
252 Remotecore will only power up the device after all the resource table's
255 In addition to system resources, the resource table may also contain
256 resource entries that publish the existence of supported features
260 The resource table begins with this header::
263 * struct resource_table - firmware resource table header
265 * @num: number of resource entries
267 * @offset: array of offsets pointing at the various resource entries
269 * The header of the resource table, as expressed by this structure,
[all …]
|
| /Documentation/virt/gunyah/ |
| D | index.rst | 86 Capabilities which are typically never given out by the Resource Manager (RM).
91 Resource Manager
94 The Gunyah Resource Manager (RM) is a privileged application VM supporting the
96 system. The resource manager can be treated as an extension of the Hypervisor
99 the platform. The resource manager runs at arm64 NS-EL1, similar to other
102 Communication with the resource manager from other virtual machines happens as
118 The source for the resource manager is available at
119 https://github.com/quic/gunyah-resource-manager.
121 The resource manager provides the following features:
127 - Resource (capability) discovery
[all …]
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | qcom,cmd-db.yaml | 10 Command DB is a database that provides a mapping between resource key and the
11 resource address for a system resource managed by a remote processor. The data
16 resource properties may change. These properties are dynamically probed by the
|
| /Documentation/translations/zh_CN/doc-guide/ |
| D | contributing.rst | 48 - Resource-managed devfreq_register_notifier()
50 - Resource-managed devfreq_unregister_notifier()
58 - Resource-managed devfreq_register_notifier()
76 - Resource-managed devfreq_register_notifier()
78 - Resource-managed devfreq_unregister_notifier()
95 - - Resource-managed devfreq_register_notifier()
96 + * - Resource-managed devfreq_register_notifier()
104 - - Resource-managed devfreq_unregister_notifier()
105 + * - Resource-managed devfreq_unregister_notifier()
|
| /Documentation/driver-api/ |
| D | men-chameleon-bus.rst | 14 3 Resource handling
41 that only use a single memory resource and share the PCI legacy IRQ. Not
44 - Multi-resource MCB devices like the VME Controller or M-Module carrier.
90 are allocated and their resources are assigned according to the resource
91 assignment in the Chameleon table. After resource assignment is finished, the
95 Resource handling
98 The current implementation assigns exactly one memory and one IRQ resource
104 Each MCB device has exactly one memory resource, which can be requested from
105 the MCB bus. This memory resource is the physical address of the MCB device
112 Each MCB device has exactly one IRQ resource, which can be requested from the
|
| /Documentation/arch/powerpc/ |
| D | associativity.rst | 2 NUMA resource associativity
13 PAPR interface currently supports different ways of communicating these resource
29 device tree properties are used to determine the NUMA distance between resource groups/domains.
32 representing the resource’s platform grouping domains.
36 The list of domainID indexes represents an increasing hierarchy of resource grouping.
44 level of the resource group, the kernel doubles the NUMA distance between the
53 ids at the same domainID index representing resource groups of different performance/latency
72 distance between resource groups/domains present in the system.
|
| /Documentation/dev-tools/kunit/api/ |
| D | resource.rst | 4 Resource API
7 This file documents the KUnit resource API.
12 .. kernel-doc:: include/kunit/resource.h
|
| D | index.rst | 10 resource
27 Documentation/dev-tools/kunit/api/resource.rst
29 - Documents the KUnit resource API
|
| /Documentation/devicetree/bindings/bus/ |
| D | st,stm32mp25-rifsc.yaml | 7 title: STM32 Resource isolation framework security controller
13 Resource isolation framework (RIF) is a comprehensive set of hardware blocks
19 - RISC registers associated with RISUP logic (resource isolation device unit
22 - RIMC registers: associated with RIMU logic (resource isolation master
28 - RISC registers associated with RISAL logic (resource isolation device unit
|
| /Documentation/devicetree/bindings/dma/ti/ |
| D | k3-pktdma.yaml | 76 Array of PKTDMA split tx channel resource subtypes for resource allocation
87 Array of PKTDMA split tx flow resource subtypes for resource allocation
98 Array of PKTDMA split rx channel resource subtypes for resource allocation
109 Array of PKTDMA split rx flow resource subtypes for resource allocation
|
| /Documentation/PCI/ |
| D | acpi-info.rst | 24 ACPI resource description is done via _CRS objects of devices in the ACPI
26 _CRS and figure out what resource is being consumed even if it doesn't have
120 information about current and possible resource requirements, the
124 When OSPM enumerates a device, it calls _PRS to determine the resource
126 resource settings for the device. Using this information, the Plug and
133 taken from the nearest matching resource above the device in the device
143 * 1 – This device consumes this resource
144 * 0 – This device produces and consumes this resource
156 4.1.3) must be reserved by declaring a motherboard resource. For most
157 systems, the motherboard resource would appear at the root of the ACPI
[all …]
|
| /Documentation/arch/x86/ |
| D | resctrl.rst | 5 User Interface for Resource Control feature
14 Intel refers to this feature as Intel Resource Director Technology(Intel(R) RDT).
21 RDT (Resource Director Technology) Allocation "rdt_a"
65 and allocation, see the "Resource alloc and monitor groups" section.
71 resources. Each resource has its own subdirectory. The subdirectory
72 names reflect the resource names.
77 Cache resource(L3/L2) subdirectory contains the following files
82 resource. The kernel uses the smallest number of
85 The bitmask which is valid for this resource.
92 Bitmask of shareable resource with other executing
[all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pmc.txt | 22 - reg: For devices compatible with "fsl,mpc8349-pmc", the first resource
23 is the PMC block, and the second resource is the Clock Configuration
26 For devices compatible with "fsl,mpc8548-pmc", the first resource
30 resource is the PMC block interrupt.
|
| /Documentation/accounting/ |
| D | psi.rst | 19 such resource crunches and the time impact it has on complex workloads
22 Having an accurate measure of productivity losses caused by resource
37 Pressure information for each resource is exported through the
46 tasks are stalled on a given resource.
49 tasks are stalled on a given resource simultaneously. In this state
70 Users can register triggers and use poll() to be woken up when resource
78 /proc/pressure/ representing the resource to be monitored and write the
109 window size must be a multiple of 2s, in order to prevent excessive resource
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-resource_in_use | 9 current status of the given power resource (0 means that the
10 resource is not in use and therefore it has been turned off).
|
| /Documentation/devicetree/bindings/mfd/ |
| D | altera-a10sr.txt | 1 * Altera Arria10 Development Kit System Resource Chip
7 System Resource chip
37 resource-manager@0 {
|
| /Documentation/netlink/specs/ |
| D | devlink.yaml | 154 name: resource-unit
433 name: resource-list
435 nested-attributes: dl-resource-list
437 name: resource
440 nested-attributes: dl-resource
442 name: resource-name
445 name: resource-id
448 name: resource-size
451 name: resource-size-new
454 name: resource-size-valid
[all …]
|
12345678910>>...15