Home
last modified time | relevance | path

Searched full:worse (Results 1 – 25 of 187) sorted by relevance

12345678

/linux/Documentation/scsi/
H A Dqlogicfas.rst63 any problem worse.
78 the computer was left on for a few hours. It was worse with longer
/linux/scripts/
H A Dremove-stale-files12 # What is worse, some people send a wrong patch to get them back to .gitignore
/linux/Documentation/devicetree/bindings/regulator/
H A Drichtek,rt4831-regulator.yaml23 efficiency worse. It's a trade-off.
/linux/tools/virtio/asm/
H A Dbarrier.h8 /* Atomic store should be enough, but gcc generates worse code in that case. */
/linux/Documentation/firmware-guide/acpi/
H A Dosi.rst128 Not to be out-done, the Linux community made things worse by returning TRUE
129 to _OSI("Linux"). Doing so is even worse than the Windows misuse
/linux/net/sched/
H A Dem_cmp.c48 * to get worse. Visit again. in em_cmp_match()
/linux/fs/ubifs/
H A DKconfig35 LZO compressor is generally faster than zlib but compresses worse.
/linux/lib/
H A Dcache_maint.c11 * race exists but this is no worse than the case where the operations instance
/linux/Documentation/i2c/busses/
H A Di2c-ali15x3.rst117 powering off the computer. It appears to be worse when the board
/linux/Documentation/filesystems/
H A Dinotify.rst24 the file and thus, worse, pins the mount. Dnotify is therefore infeasible
/linux/arch/arm/mach-omap2/
H A Dtimer.c98 * should compensate to avoid the 570ppm (at 20MHz, much worse in realtime_counter_init()
/linux/Documentation/usb/
H A Dauthorization.rst65 checking if the class, type and protocol match something is the worse
/linux/include/linux/
H A Dcompiler-clang.h141 * inputs, turning them into something worse than "m". Avoid using
/linux/drivers/block/drbd/
H A Ddrbd_vli.h37 * integers would be much worse than plaintext.
77 * last level (+1 data bit, so it makes 64bit total). The only worse code when
/linux/tools/power/cpupower/bench/
H A DREADME-BENCH19 throughput is, the worse the power savings will be, but the first should
/linux/kernel/trace/
H A Dtrace_recursion_record.c105 * But the worse that could happen is that we get a zero in in ftrace_record_recursion()
/linux/Documentation/RCU/
H A Dlockdep-splat.rst17 overwriting or worse. There can of course be false positives, this
/linux/arch/m68k/q40/
H A DREADME125 Unfortunately the AT->PC translation isn't quite trivial and even worse, my
/linux/Documentation/arch/riscv/
H A Dcmodx.rst25 RISC-V ftrace. Kernel preemption makes things even worse as it allows the old
/linux/include/uapi/linux/
H A Dfdreg.h135 * assign FDC_UNKNOWN. Else the FDC will be treated as a dumb 8272a, or worse.
/linux/arch/powerpc/include/asm/
H A Dparavirt.h56 * first instance (or worse: queued spinlocks use tricks that assume a context
/linux/usr/
H A DKconfig178 better than that of bzip2 but worse than gzip and LZO. Compression is
/linux/Documentation/locking/
H A Dspinlocks.rst105 and on other architectures it can be worse).
/linux/fs/afs/
H A Dmain.c216 * a transport upon the first mount, which is worse. Or is it?
/linux/fs/notify/inotify/
H A Dinotify_fsnotify.c169 * out why we got here and the panic is no worse than the original in idr_callback()

12345678