| /Linux-v5.4/net/dccp/ |
| D | qpolicy.c | 48 struct sk_buff *skb, *worst = NULL; in qpolicy_prio_worst_skb() local
51 if (worst == NULL || skb->priority < worst->priority) in qpolicy_prio_worst_skb()
52 worst = skb; in qpolicy_prio_worst_skb()
53 return worst; in qpolicy_prio_worst_skb()
|
| /Linux-v5.4/arch/h8300/lib/ |
| D | mulsi3.S | 9 ; 16b * 16b = 372 states (worst case)
10 ; 32b * 32b = 724 states (worst case)
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/ |
| D | domain-idle-state.txt | 16 Definition: u32 value representing worst case latency in
24 Definition: u32 value representing worst case latency
|
| /Linux-v5.4/arch/x86/boot/ |
| D | header.S | 503 # The worst case at the block level is a growth of the compressed data
506 # The worst case internal to a compressed block is very hard to figure.
507 # The worst case can at least be bounded by having one bit that represents
514 # block adding an extra 32767 bytes (the worst case uncompressed block size)
515 # is sufficient, to ensure that in the worst case the decompressed data for
|
| /Linux-v5.4/arch/x86/kernel/cpu/mce/ |
| D | core.c | 1140 int no_way_out, int *worst) in __mc_scan_banks() argument
1196 if (severity > *worst) { in __mc_scan_banks()
1198 *worst = severity; in __mc_scan_banks()
1226 int worst = 0; in do_machine_check() local
1299 __mc_scan_banks(&m, final, toclear, valid_banks, no_way_out, &worst); in do_machine_check()
1310 no_way_out = worst >= MCE_PANIC_SEVERITY; in do_machine_check()
1320 if (worst >= MCE_PANIC_SEVERITY && mca_cfg.tolerant < 3) { in do_machine_check()
1335 if (worst > 0) in do_machine_check()
1342 if (worst != MCE_AR_SEVERITY && !kill_it) in do_machine_check()
|
| /Linux-v5.4/Documentation/x86/x86_64/ |
| D | cpu-hotplug-spec.rst | 21 In the worst case the user can overwrite this choice using a command line
|
| /Linux-v5.4/tools/power/cpupower/bench/ |
| D | README-BENCH | 7 - Identify worst case performance loss when doing dynamic frequency
84 will always see 50% loads and you get worst performance impact never
|
| /Linux-v5.4/Documentation/devicetree/bindings/regulator/ |
| D | vctrl.txt | 29 down in the worst case (lightest expected load).
|
| /Linux-v5.4/drivers/block/mtip32xx/ |
| D | mtip32xx.h | 167 u8 worst; member
|
| /Linux-v5.4/arch/x86/math-emu/ |
| D | README | 239 each function was tested at about 400 points. Ideal worst-case results
307 worst-case results which are better than the worst-case results given
321 the worst accuracy which was found (in bits) and the approximate value
326 instr arg range # tests 63.7 63.8 63.9 worst at arg
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| D | cafe_ccic.rst | 38 then worst-case-sized buffers will be allocated at module load time.
|
| /Linux-v5.4/Documentation/vm/ |
| D | zsmalloc.rst | 23 worst case, page is incompressible and is thus stored "as-is" i.e. in
|
| D | ksm.rst | 62 deduplication factor at the expense of slower worst case for rmap
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/ |
| D | idle-states.txt | 106 the worst case since it depends on the CPU operating conditions, i.e. caches
111 worst case wake-up latency it can incur if a CPU is allowed to enter an
288 Definition: u32 value representing worst case latency in
294 Definition: u32 value representing worst case latency
|
| /Linux-v5.4/Documentation/timers/ |
| D | timers-howto.rst | 94 worst case, fire an interrupt for your upper bound.
|
| /Linux-v5.4/arch/arm/nwfpe/ |
| D | ChangeLog | 44 * I discovered several bugs. First and worst is that the kernel
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | pixfmt-v4l2-mplane.rst | 37 codec to support the worst-case compression scenario.
|
| D | pixfmt-v4l2.rst | 97 number of bytes required by the codec to support the worst-case
|
| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| D | log-writes.rst | 26 simulate the worst case scenario with regard to power failures. Consider the
|
| /Linux-v5.4/Documentation/arm64/ |
| D | memory.rst | 147 the "worst" case.
|
| /Linux-v5.4/Documentation/security/ |
| D | self-protection.rst | 13 In the worst-case scenario, we assume an unprivileged local attacker
16 but with systems in place that defend against the worst case we'll
|
| /Linux-v5.4/Documentation/ |
| D | pi-futex.txt | 25 determinism and well-bound latencies. Even in the worst-case, PI will
|
| /Linux-v5.4/Documentation/process/ |
| D | 6.Followthrough.rst | 128 is that conflicts with work being done by others turn up. In the worst
157 The worst sort of bug reports are regressions. If your patch causes a
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | eeh-pci-error-recovery.rst | 97 reinitialization of the device driver. In a worst-case scenario,
105 kernel/device driver should assume the worst-case scenario, that the
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | ksm.rst | 141 deduplication factor will be, but the slower the worst case
|
