Searched full:classes (Results 1 – 25 of 100) sorted by relevance
1234
| /Documentation/mm/ |
| D | zsmalloc.rst | 40 # cat /sys/kernel/debug/zsmalloc/zram0/classes
98 zsmalloc has 255 size classes, each of which can hold a number of zspages.
103 As an optimization, zsmalloc merges size classes that have similar
107 For instance, consider the following size classes:::
116 Size classes #95-99 are merged with size class #100. This means that when we
144 dewer class mergers, resulting in a more compact grouping of classes, which
147 Let's take a closer look at the bottom of `/sys/kernel/debug/zsmalloc/zramX/classes`:::
159 in huge classes do not share pages).
162 for the huge size class and fewer huge classes overall. This allows for more
207 pages per zspage number of size classes (clusters) huge size class watermark
[all …]
|
| /Documentation/scsi/ |
| D | megaraid.rst | 10 Different classes of controllers from LSI Logic accept and respond to the
12 commands. Furthermore, the applications also can treat different classes of
77 as new controller classes get added, this will be tuned appropriately.
|
| /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
157 between any two lock-classes::
324 is O(N^2), so even with just a few hundred lock-classes we'd have to do
339 The validator tracks a maximum of MAX_LOCKDEP_KEYS number of lock classes.
345 desktop systems have less than 1,000 lock classes, so this warning
351 load of the module will create a new set of lock classes for
353 classes (see below discussion of reuse of lock classes for why).
355 the number of lock classes will eventually reach the maximum.
360 spinlock_t will consume 8192 lock classes -unless- each spinlock
[all …]
|
| /Documentation/sphinx/ |
| D | kernel_include.py | 157 classes=self.options.get('class', []))
170 for classes, value in tokens:
171 if classes:
173 classes=classes)
|
| D | rstFlatTable.py | 188 def buildTableRowNode(self, row_data, classes=None): argument
189 classes = [] if classes is None else classes
196 attributes = {"classes" : classes}
|
| /Documentation/ABI/testing/ |
| D | sysfs-class | 6 subdirectories describing individual classes of devices
|
| D | evm | 11 EVM supports two classes of security.evm. The first is
|
| /Documentation/userspace-api/media/v4l/ |
| D | extended-controls.rst | 32 Extended Control API, nowadays there are also other classes of Extended
34 Extended Controls API as well as all Extended Controls classes are
54 controls in that array and a control class. Control classes are used to
|
| D | vidioc-g-ctrl.rst | 53 These ioctls work only with user controls. For other control classes the
|
| /Documentation/translations/zh_CN/mm/ |
| D | zsmalloc.rst | 38 # cat /sys/kernel/debug/zsmalloc/zram0/classes
|
| /Documentation/networking/device_drivers/ethernet/freescale/ |
| D | dpaa.rst | 162 The driver has support for multiple prioritized Tx traffic classes. Priorities
166 are used. Higher priority traffic classes can be enabled with the mqprio
167 qdisc. For example, all four traffic classes are enabled on an interface with
169 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/devicetree/bindings/net/ |
| D | fsl,enetc.yaml | 12 (SR-IOV), advanced QoS with 8 traffic classes and 4 drop resilience levels,
|
| /Documentation/block/ |
| D | ioprio.rst | 14 Scheduling classes
17 Three generic scheduling classes are implemented for io priorities that
|
| /Documentation/userspace-api/ |
| D | tee.rst | 30 There are two classes of clients, normal clients and supplicants. The latter is
|
| /Documentation/scheduler/ |
| D | sched-design-CFS.rst | 151 6. SCHEDULING CLASSES
155 Classes," an extensible hierarchy of scheduler modules. These modules
166 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/networking/device_drivers/ethernet/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/ethernet/marvell/ |
| D | octeontx2.rst | 304 once the usercreates tc classes with different priorities, the driver configures
330 3. Create tc classes with different priorities::
336 4. Create tc classes with same priorities and different quantum::
|
| /Documentation/networking/device_drivers/ethernet/ti/ |
| D | cpsw.rst | 27 - Traffic classes are used starting from 0, that has highest priority
35 - Any l2/socket prio (0 - 7) for classes can be used, but for
37 - only 2 classes tested: A and B, but checked and can work with more,
54 | Only 2 classes: |Mb +---| +-------------------------------+
210 // Check classes settings
437 // Check classes settings
496 // Check classes settings
|
| /Documentation/process/ |
| D | index.rst | 77 of special classes of bugs: regressions and security problems.
|
| /Documentation/arch/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> - which contain
|
| /Documentation/arch/x86/x86_64/ |
| D | fake-numa-for-cpusets.rst | 77 interesting combinations of use-cases for various classes of tasks for your
|
| /Documentation/wmi/devices/ |
| D | msi-wmi-platform.rst | 23 Description("This class contains the definition of the package used in other classes"),
30 Description("This class contains the definition of the package used in other classes"),
|
1234