| /openbmc/linux/Documentation/trace/ |
| H A D | events-kmem.rst | 60 amounts of activity imply high activity on the zone->lock. Taking this lock
65 is triggered. Significant amounts of activity here could indicate that the
70 freed in batch with a page list. Significant amounts of activity here could
95 consecutively imply the zone->lock being taken once. Large amounts of per-CPU
98 lists should be a larger size. Finally, large amounts of refills on one CPU
99 and drains on another could be a factor in causing large amounts of cache
|
| H A D | events-nmi.rst | 14 NMI handlers are hogging large amounts of CPU time. The kernel
|
| /openbmc/linux/Documentation/devicetree/bindings/phy/ |
| H A D | qcom,usb-snps-femto-v2.yaml | 94 unit amounts. One unit of pre-emphasis duration is approximately
106 amounts. One unit amount is approximately 2 mA and is defined as
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/md5deep/ |
| H A D | md5deep_git.bb | 1 SUMMARY = "md5deep and hashdeep to compute and audit hashsets of amounts of files."
|
| /openbmc/linux/kernel/module/ |
| H A D | Makefile | 7 # and produce insane amounts of uninteresting coverage.
|
| /openbmc/linux/tools/testing/selftests/zram/ |
| H A D | README | 8 good amounts of memory savings. Some of the usecases include /tmp storage,
|
| /openbmc/linux/arch/sh/include/uapi/asm/ |
| H A D | stat.h | 41 * insane amounts of padding around dev_t's.
|
| /openbmc/linux/arch/m68k/include/uapi/asm/ |
| H A D | stat.h | 43 * insane amounts of padding around dev_t's.
|
| /openbmc/linux/arch/x86/include/asm/ |
| H A D | ia32.h | 27 * insane amounts of padding around dev_t's.
|
| /openbmc/linux/arch/arm/include/uapi/asm/ |
| H A D | stat.h | 53 * insane amounts of padding around dev_t's.
|
| /openbmc/u-boot/lib/efi/ |
| H A D | Kconfig | 35 other smaller amounts) and it can never be increased after that.
|
| /openbmc/linux/include/crypto/ |
| H A D | sm3.h | 43 * amounts of data as those APIs may be hw-accelerated.
|
| H A D | sha2.h | 98 * amounts of data as those APIs may be hw-accelerated.
|
| /openbmc/linux/arch/x86/entry/ |
| H A D | entry.S | 56 * amounts to the whole of vmlinux with LTO enabled), Clang will drop the
|
| /openbmc/linux/arch/s390/include/uapi/asm/ |
| H A D | stat.h | 50 * insane amounts of padding around dev_t's.
|
| /openbmc/linux/drivers/block/zram/ |
| H A D | Kconfig | 11 good amounts of memory savings.
|
| /openbmc/linux/arch/x86/include/uapi/asm/ |
| H A D | stat.h | 40 * insane amounts of padding around dev_t's.
|
| /openbmc/linux/arch/mips/include/uapi/asm/ |
| H A D | stat.h | 48 * amounts of padding around dev_t's. The memory layout is the same as of
|
| /openbmc/linux/drivers/dma-buf/ |
| H A D | Kconfig | 49 problem where userspace is able to pin unrestricted amounts of memory
|
| /openbmc/linux/Documentation/fb/ |
| H A D | efifb.rst | 44 when large amounts of console data are written.
|
| /openbmc/qemu/docs/system/ |
| H A D | target-openrisc.rst | 45 and large amounts of RAM.
|
| H A D | target-riscv.rst | 51 large amounts of RAM. It also supports 64-bit CPUs.
|
| /openbmc/u-boot/doc/ |
| H A D | README.bloblist | 32 hold small amounts of data, typically a few KB at most. It is not possible to
|
| /openbmc/qemu/migration/ |
| H A D | migration-stats.h | 40 * the remaining dirty amounts to what we know that is still dirty
|
| /openbmc/u-boot/board/armltd/integrator/ |
| H A D | README | 21 CMs may be fitted with varying amounts of SDRAM using a DIMM socket.
|