Searched refs:penalty (Results 1 – 25 of 34) sorted by relevance
12
460 int penalty = 0; in acpi_irq_pci_sharing_penalty() local469 penalty += PIRQ_PENALTY_PCI_USING; in acpi_irq_pci_sharing_penalty()476 penalty += PIRQ_PENALTY_PCI_POSSIBLE / in acpi_irq_pci_sharing_penalty()480 return penalty; in acpi_irq_pci_sharing_penalty()485 int penalty = 0; in acpi_irq_get_penalty() local488 penalty += sci_penalty; in acpi_irq_get_penalty()491 return penalty + acpi_isa_irq_penalty[irq]; in acpi_irq_get_penalty()493 return penalty + acpi_irq_pci_sharing_penalty(irq); in acpi_irq_get_penalty()511 int penalty = in acpi_irq_penalty_init() local519 penalty; in acpi_irq_penalty_init()
20 require action at a specific point, no penalty will be paid for
19 "off" it has no effect, except for adding a tiny time penalty20 (checking a condition for a branch) and space penalty (adding a few
20 penalty to the core scheduler implementation in the CONFIG_SMP case.
30 performance penalty but still allow for runtime (rather than compile-time) CPU
97 in a significant performance penalty.
118 - You know that the penalty of TLB misses while accessing the
29 lock prefix and the associated latency penalty.
70 Defines the penalty which will be applied to an
79 avoids a potential TLB penalty. The downside is an increase in
34 on the seek penalty when the filesystem first has to read a file's inode
67 with video capturing hardware) may incur a performance penalty
117 slight CPU penalty when too many bit-flips are detected during reads.
47 some performance penalty. Also, it is generally not possible to point to
504 __u32 penalty; member
95 buffer size, which may be a needless performance penalty for callers using
95 penalty; they do not belong in the Linux kernel.
503 __u32 penalty; member
117 performance penalty or wear of flash device
76 performance penalty, whether on separate cards or a single VLB card.
127 penalty. For disk drives this is often the physical
202 ! However the penalty for getting it 'wrong' is much higher for long word
38 # extra layer of hierarchy adds a slight performance penalty but
16 - performance: minimize the performance penalty imposed by the mmu
199 caches safe to use, at some performance penalty. If your disks are
