Searched full:classes (Results 1 – 25 of 78) sorted by relevance
1234
| /Documentation/locking/ |
| D | lockdep-design.rst | 19 The validator tracks the 'usage state' of lock-classes, and it tracks
20 the dependencies between different lock-classes. Lock usage indicates
154 between any two lock-classes::
321 is O(N^2), so even with just a few hundred lock-classes we'd have to do
336 The validator tracks a maximum of MAX_LOCKDEP_KEYS number of lock classes.
342 desktop systems have less than 1,000 lock classes, so this warning
348 load of the module will create a new set of lock classes for
350 classes (see below discussion of reuse of lock classes for why).
352 the number of lock classes will eventually reach the maximum.
357 spinlock_t will consume 8192 lock classes -unless- each spinlock
[all …]
|
| /Documentation/driver-api/driver-model/ |
| D | class.rst | 2 Device Classes
8 device. The following device classes have been identified:
10 <Insert List of Device Classes Here>
18 Device classes are agnostic with respect to what bus a device resides
43 Device classes are registered and unregistered with the core using::
74 Device drivers are added to device classes when they are registered
|
| /Documentation/scsi/ |
| D | megaraid.txt | 7 Different classes of controllers from LSI Logic accept and respond to the
9 commands. Furthermore, the applications also can treat different classes of
70 as new controller classes get added, this will be tuned appropriately.
|
| /Documentation/sphinx/ |
| D | kernel_include.py | 155 classes=self.options.get('class', []))
168 for classes, value in tokens:
169 if classes:
171 classes=classes)
|
| D | rstFlatTable.py | 198 def buildTableRowNode(self, row_data, classes=None): argument
199 classes = [] if classes is None else classes
206 attributes = {"classes" : classes}
|
| D | automarkup.py | 54 lit_text = nodes.literal(classes=['xref', 'c', 'c-func'])
|
| /Documentation/ABI/testing/ |
| D | sysfs-class | 6 subdirectories describing individual classes of devices
|
| D | evm | 10 EVM supports two classes of security.evm. The first is
|
| D | sysfs-firmware-acpi | 25 There are separate hotplug profiles for different classes of
|
| /Documentation/media/uapi/v4l/ |
| D | extended-controls.rst | 39 Extended Control API, nowadays there are also other classes of Extended
41 Extended Controls API as well as all Extended Controls classes are
61 controls in that array and a control class. Control classes are used to
|
| D | vidioc-g-ctrl.rst | 60 These ioctls work only with user controls. For other control classes the
|
| /Documentation/networking/device_drivers/freescale/ |
| D | dpaa.txt | 156 The driver has support for multiple prioritized Tx traffic classes. Priorities
160 are used. Higher priority traffic classes can be enabled with the mqprio
161 qdisc. For example, all four traffic classes are enabled on an interface with
163 classes as follows:
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/ |
| D | i2c.txt | 22 being used. The definition of the classes can be found in
|
| /Documentation/block/ |
| D | ioprio.rst | 15 Scheduling classes
18 CFQ implements three generic scheduling classes that determine how io is
|
| /Documentation/scheduler/ |
| D | sched-design-CFS.rst | 144 6. SCHEDULING CLASSES
148 Classes," an extensible hierarchy of scheduler modules. These modules
159 Scheduling classes are implemented through the sched_class structure, which
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | net_prio.rst | 53 traffic to be steered to hardware/driver based traffic classes. These mappings
|
| /Documentation/vm/ |
| D | zsmalloc.rst | 42 # cat /sys/kernel/debug/zsmalloc/zram0/classes
|
| /Documentation/networking/device_drivers/intel/ |
| D | iavf.rst | 155 1. Create traffic classes (TCs). Maximum of 8 TCs can be created per interface.
251 Using four traffic classes fails
253 Do not try to reserve more than three traffic classes in the iavf driver. Doing
254 so will fail to set any traffic classes and will cause the driver to write
|
| D | ixgbe.rst | 232 the DCB features (multiple traffic classes utilizing Priority Flow Control and
236 multiple traffic classes (packet buffers in the NIC). The traffic is associated
243 receive/transmit descriptor queue pairs. When multiple traffic classes are
249 classes that can be enabled. The configurable number of traffic classes for
251 0 - 15 VFs = Up to 8 traffic classes, depending on device support
252 16 - 31 VFs = Up to 4 traffic classes
|
| /Documentation/networking/device_drivers/ti/ |
| D | cpsw.txt | 22 - Traffic classes are used starting from 0, that has highest priority
30 - Any l2/socket prio (0 - 7) for classes can be used, but for
32 - only 2 classes tested: A and B, but checked and can work with more,
46 | Only 2 classes: |Mb +---| +-------------------------------+
193 // Check classes settings
406 // Check classes settings
458 // Check classes settings
|
| /Documentation/x86/x86_64/ |
| D | fake-numa-for-cpusets.rst | 77 interesting combinations of use-cases for various classes of tasks for your
|
| /Documentation/arm/ |
| D | arm.rst | 184 We group machine (or platform) support code into machine classes. A
187 classes are given directories - arch/arm/mach-<class> and
|
| /Documentation/arm64/ |
| D | pointer-authentication.rst | 17 used to mitigate certain classes of attack where an attacker can corrupt
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | panel-common.yaml | 14 This document defines device tree properties common to several classes of
|
| /Documentation/driver-api/ |
| D | scsi.rst | 229 Transport classes
232 Transport classes are service libraries for drivers in the SCSI lower
|
1234