| /linux/net/dccp/ |
| H A D | qpolicy.c | |
| /linux/arch/x86/boot/ |
| H A D | header.S | 453 # The worst case at the block level is a growth of the compressed data
456 # The worst case internal to a compressed block is very hard to figure.
457 # The worst case can at least be bounded by having one bit that represents
464 # block adding an extra 32767 bytes (the worst case uncompressed block size)
465 # is sufficient, to ensure that in the worst case the decompressed data for
|
| /linux/arch/x86/kernel/cpu/mce/ |
| H A D | core.c | 1359 unsigned long *valid_banks, int no_way_out, int *worst) in __mc_scan_banks() argument
1422 if (severity > *worst) { in __mc_scan_banks()
1424 *worst = severity; in __mc_scan_banks()
1556 int worst = 0, order, no_way_out, kill_current_task, lmce, taint = 0; in do_machine_check() local
1640 taint = __mc_scan_banks(&err, regs, final, toclear, valid_banks, no_way_out, &worst); in do_machine_check()
1652 no_way_out = worst >= MCE_PANIC_SEVERITY; in do_machine_check()
1666 if (worst >= MCE_PANIC_SEVERITY) { in do_machine_check()
1682 if (worst != MCE_AR_SEVERITY && !kill_current_task) in do_machine_check()
|
| /linux/tools/power/cpupower/bench/ |
| H A 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/Documentation/arch/x86/x86_64/ |
| H A D | cpu-hotplug-spec.rst | 21 In the worst case the user can overwrite this choice using a command line
|
| /linux/tools/testing/selftests/net/packetdrill/ |
| H A D | tcp_zerocopy_maxfrags.pkt | 19 // This test generates a worst case packet with each frag storing
|
| /linux/drivers/block/mtip32xx/ |
| H A D | mtip32xx.h | 165 u8 worst; member
|
| /linux/arch/x86/math-emu/ |
| H A 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/Documentation/hwmon/ |
| H A D | stpddc60.rst | 41 writing to those limits since in the worst case the commanded output voltage
|
| /linux/Documentation/admin-guide/media/ |
| H A D | cafe_ccic.rst | 38 then worst-case-sized buffers will be allocated at module load time.
|
| /linux/Documentation/tools/rtla/ |
| H A D | rtla-hwnoise.rst | 74 for the application. In the worst single period, the CPU caused *4 us* of
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | pixfmt-v4l2-mplane.rst | 31 codec to support the worst-case compression scenario.
|
| H A D | pixfmt-v4l2.rst | 96 number of bytes required by the codec to support the worst-case
|
| /linux/Documentation/mm/ |
| H A D | ksm.rst | 60 deduplication factor at the expense of slower worst case for rmap
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-platform-dptf | 52 (RO) Shows the rest (outside of SoC) of worst-case platform power.
|
| /linux/arch/arm/nwfpe/ |
| H A D | ChangeLog | 44 * I discovered several bugs. First and worst is that the kernel
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | log-writes.rst | 26 simulate the worst case scenario with regard to power failures. Consider the
|
| /linux/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3588-jaguar-pre-ict-tester.dtso | 106 * the worst case scenario and the pass scenario expect
|
| /linux/Documentation/security/ |
| H A 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/Documentation/process/ |
| H A D | 6.Followthrough.rst | 135 is that conflicts with work being done by others turn up. In the worst
164 The worst sort of bug reports are regressions. If your patch causes a
|
| /linux/Documentation/locking/ |
| H A D | pi-futex.rst | 25 determinism and well-bound latencies. Even in the worst-case, PI will
|
| /linux/Documentation/filesystems/nfs/ |
| H A D | nfsd-io-modes.rst | 80 system memory. The pathological worst-case workload that NFSD DIRECT has
|
| /linux/Documentation/driver-api/usb/ |
| H A D | persist.rst | 24 device plugged into the port. The system must assume the worst.
|
| /linux/drivers/scsi/esas2r/ |
| H A D | atvda.h | 511 u8 worst; member
|
| /linux/Documentation/core-api/ |
| H A D | maple_tree.rst | 202 allocate the worst-case number of needed nodes to insert the provided number of
|