Searched full:worthwhile (Results 1 – 25 of 45) sorted by relevance
12
| /Linux-v5.15/include/xen/interface/io/ |
| D | blkif.h | 90 * or not it is worthwhile for the frontend to attempt barrier requests.
104 * is worthwhile for the frontend to attempt flushes. If a backend does
117 * or not it is worthwhile for the frontend to attempt discard requests.
|
| /Linux-v5.15/arch/x86/include/asm/ |
| D | qspinlock_paravirt.h | 9 * hand-coded for 64-bit, but it isn't worthwhile to do it for 32-bit.
|
| /Linux-v5.15/arch/sh/kernel/ |
| D | io.c | 19 * Would it be worthwhile doing byte and long transfers first in memcpy_fromio()
|
| /Linux-v5.15/include/linux/ |
| D | compaction.h | 145 * worthwhile, but with a higher priority if allowed.
|
| /Linux-v5.15/lib/raid6/ |
| D | sse1.c | 16 * worthwhile as a separate implementation.
|
| /Linux-v5.15/arch/arm/lib/ |
| D | uaccess_with_memcpy.c | 226 * so far the measurement on concerned targets didn't show a worthwhile
|
| /Linux-v5.15/Documentation/scsi/ |
| D | FlashPoint.rst | 129 not convinced that the effort required would be worthwhile.
|
| /Linux-v5.15/Documentation/accounting/ |
| D | taskstats.rst | 158 extending the attributes structure would be worthwhile.
|
| /Linux-v5.15/Documentation/devicetree/bindings/arm/ |
| D | idle-states.yaml | 91 idle state to be worthwhile energywise.
299 and entry, for this idle state to be considered worthwhile energy wise
|
| /Linux-v5.15/Documentation/process/ |
| D | 7.AdvancedTopics.rst | 178 welcome and worthwhile.
|
| D | management-style.rst | 93 wasn't worthwhile after all can be hard on the poor lowly engineers
|
| /Linux-v5.15/fs/verity/ |
| D | verify.c | 284 * locality, but it's worthwhile since hashing is CPU-intensive. in fsverity_init_workqueue()
|
| /Linux-v5.15/arch/sh/lib/ |
| D | memcpy-sh4.S | 196 ! using the optimised routines become worthwhile varies (these are the
239 ! Size is not small, so its worthwhile looking for optimisations.
|
| /Linux-v5.15/Documentation/hwmon/ |
| D | lm85.rst | 124 measurements, so this would seem to be a worthwhile optimization.
|
| /Linux-v5.15/fs/crypto/ |
| D | crypto.c | 368 * locality, but it's worthwhile since decryption is CPU-intensive. in fscrypt_init()
|
| /Linux-v5.15/arch/alpha/include/asm/ |
| D | bitops.h | 297 * constants on the alpha, it is worthwhile to split the search.
|
| /Linux-v5.15/arch/m68k/sun3/ |
| D | mmu_emu.c | 278 //todo: better allocation scheme? but is extra complexity worthwhile?
|
| /Linux-v5.15/Documentation/arm64/ |
| D | memory-tagging-extension.rst | 134 worthwhile to enable stricter checks on those CPUs when a less strict
|
| /Linux-v5.15/arch/arm/include/asm/ |
| D | assembler.h | 75 * XScale didn't show this a worthwhile thing to do when the cache is not
|
| /Linux-v5.15/arch/x86/kernel/ |
| D | ldt.c | 565 * is worthwhile, disallow 16-bit segments under Xen PV. in allow_16bit_segments()
|
| /Linux-v5.15/fs/ntfs3/lib/ |
| D | lzx_decompress.c | 175 * A worthwhile optimization is to push the end-of-buffer check into the in lzx_postprocess()
|
| /Linux-v5.15/lib/ |
| D | idr.c | 353 * is a worthwhile optimisation; Rasmus Villemoes surveyed the current
|
| /Linux-v5.15/Documentation/filesystems/ |
| D | ext2.rst | 206 This is a worthwhile optimisation as it we avoid allocating a full
|
| /Linux-v5.15/Documentation/RCU/ |
| D | checklist.rst | 51 complexity is worthwhile. If you choose #c, be prepared to
|
| /Linux-v5.15/fs/ubifs/ |
| D | commit.c | 354 * worthwhile, so background thread is kicked to start it.
|
12
