| /Linux-v5.10/drivers/acpi/ |
| D | pci_link.c | 458 int penalty = 0; in acpi_irq_pci_sharing_penalty() local
467 penalty += PIRQ_PENALTY_PCI_USING; in acpi_irq_pci_sharing_penalty()
474 penalty += PIRQ_PENALTY_PCI_POSSIBLE / in acpi_irq_pci_sharing_penalty()
478 return penalty; in acpi_irq_pci_sharing_penalty()
483 int penalty = 0; in acpi_irq_get_penalty() local
486 penalty += sci_penalty; in acpi_irq_get_penalty()
489 return penalty + acpi_isa_irq_penalty[irq]; in acpi_irq_get_penalty()
491 return penalty + acpi_irq_pci_sharing_penalty(irq); in acpi_irq_get_penalty()
509 int penalty = in acpi_irq_penalty_init() local
517 penalty; in acpi_irq_penalty_init()
|
| /Linux-v5.10/Documentation/devicetree/bindings/mtd/ |
| D | nand-macronix.txt | 5 which can be enabled with a SET_FEATURE. The penalty when using the
|
| D | gpmc-nand.txt | 117 slight CPU penalty when too many bit-flips are detected during reads.
|
| /Linux-v5.10/tools/testing/selftests/tc-testing/ |
| D | TODO.txt | 20 require action at a specific point, no penalty will be paid for
|
| /Linux-v5.10/Documentation/trace/ |
| D | tracepoints.rst | 19 "off" it has no effect, except for adding a tiny time penalty
20 (checking a condition for a branch) and space penalty (adding a few
|
| /Linux-v5.10/Documentation/scheduler/ |
| D | sched-arch.rst | 20 penalty to the core scheduler implementation in the CONFIG_SMP case.
|
| /Linux-v5.10/Documentation/powerpc/ |
| D | cpu_features.rst | 30 performance penalty but still allow for runtime (rather than compile-time) CPU
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | io-mapping.rst | 97 in a significant performance penalty.
|
| D | edac.rst | 47 some performance penalty. Also, it is generally not possible to point to
|
| /Linux-v5.10/Documentation/block/ |
| D | blk-mq.rst | 20 performance possible for those devices with a high penalty when doing random
27 without mechanical parts nor random access penalty and capable of performing
|
| /Linux-v5.10/Documentation/ABI/obsolete/ |
| D | sysfs-class-net-mesh | 70 Defines the penalty which will be applied to an
|
| /Linux-v5.10/Documentation/filesystems/ext4/ |
| D | allocators.rst | 34 on the seek penalty when the filesystem first has to read a file's inode
|
| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| D | func-mmap.rst | 58 with video capturing hardware) may incur a performance penalty
|
| /Linux-v5.10/Documentation/core-api/ |
| D | dma-attributes.rst | 92 - You know that the penalty of TLB misses while accessing the
|
| D | this_cpu_ops.rst | 29 lock prefix and the associated latency penalty.
|
| /Linux-v5.10/tools/include/uapi/linux/ |
| D | pkt_sched.h | 503 __u32 penalty; member
|
| /Linux-v5.10/Documentation/driver-api/thermal/ |
| D | cpu-idle-cooling.rst | 70 performance penalty and a fixed latency. Mitigation can be increased
|
| /Linux-v5.10/include/uapi/linux/ |
| D | pkt_sched.h | 523 __u32 penalty; member
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | nilfs2.rst | 124 performance penalty or wear of flash device
|
| /Linux-v5.10/Documentation/ide/ |
| D | ide.rst | 76 performance penalty, whether on separate cards or a single VLB card.
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-block | 137 penalty. For disk drives this is often the physical
|
| /Linux-v5.10/arch/sh/lib/ |
| D | memcpy-sh4.S | 202 ! However the penalty for getting it 'wrong' is much higher for long word
|
| /Linux-v5.10/Documentation/process/ |
| D | deprecated.rst | 125 destination buffer size, which may be a needless performance penalty
|
| /Linux-v5.10/arch/m68k/ifpsp060/src/ |
| D | isp.S | 38 # extra layer of hierarchy adds a slight performance penalty but
|
| /Linux-v5.10/Documentation/virt/kvm/ |
| D | mmu.rst | 22 minimize the performance penalty imposed by the mmu
|
