Searched refs:penalty (Results 1 – 25 of 27) sorted by relevance
12
17 "off" it has no effect, except for adding a tiny time penalty18 (checking a condition for a branch) and space penalty (adding a few
42 penalty.
82 in a significant performance penalty.
99 psched_tdiff_t penalty; member507 sched += delay + cl->penalty; in cbq_ovl_delay()536 cl->penalized = q->now + cl->penalty; in cbq_ovl_lowprio()1328 cl->penalty = ovl->penalty; in cbq_set_overlimit()1492 opt.penalty = cl->penalty; in cbq_dump_ovl()
65 Defines the penalty which will be applied to an
112 penalty. For disk drives this is often the physical
26 performance penalty but still allow for runtime (rather than compile-time) CPU
494 int penalty = in acpi_irq_penalty_init() local502 penalty; in acpi_irq_penalty_init()
293 is about half of the penalty and is rarely useful.
18 penalty to the core scheduler implementation in the CONFIG_SMP case.
437 __u32 penalty; member
37 performance penalty.
69 safe to use, at some performance penalty. If
191 safe to use, at some performance penalty. If
255 protocol is configured. Thus, eliminating the performance penalty
75 performance penalty, whether on separate cards or a single VLB card.
201 ! However the penalty for getting it 'wrong' is much higher for long word
16 - performance: minimize the performance penalty imposed by the mmu
38 # extra layer of hierarchy adds a slight performance penalty but
512 be forced to incur a performance penalty in OOM conditions when the
81 penalty; they do not belong in the Linux kernel.
1074 memory they do not own. This comes at a performance penalty
499 Even with this penalty, I think that this will work great.
417 either become confused or incur a performance penalty1947 penalty to optimizing for maximum bandwidth. In this case, there is2335 cases with no connectivity, there is no additional penalty for
850 delimited by $arg$ of type $struct\ \penalty-1000 cdrom_ti *{}$.