| /openbmc/linux/Documentation/scheduler/ |
| H A D | sched-capacity.rst | 28 performance-oriented than the LITTLE ones (more pipeline stages, bigger caches,
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | thin-provisioning.rst | 416 load a target that is bigger than before, then extra blocks will be
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | initrd.rst | 319 from CD, e.g. by using a boot floppy and bootstrapping a bigger RAM disk
|
| H A D | xfs.rst | 98 not handle inode numbers bigger than 32 bits, the ``inode32``
|
| /openbmc/linux/arch/m68k/fpsp040/ |
| H A D | setox.S | 134 | Note that 0.0062 is slightly bigger than 0.57 log2/64.
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | sme.rst | 297 thread. The regset won't grow bigger than this even if the target
|
| H A D | sve.rst | 319 thread. The regset won't grow bigger than this even if the target
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | perf-script.txt | 390 will override this value if the synthesized callchain size is bigger.
|
| H A D | perf-report.txt | 291 will override this value if the synthesized callchain size is bigger.
|
| H A D | perf-record.txt | 573 Also at some cases executing less output write syscalls with bigger data size
|
| /openbmc/linux/Documentation/networking/ |
| H A D | ethtool-netlink.rst | 938 A bigger CQE can have more receive buffer pointers inturn NIC can transfer
939 a bigger frame from wire. Based on the NIC hardware, the overall completion
1336 bigger than transmitted pulse.
|
| H A D | ip-sysctl.rst | 671 On retransmit try to send bigger packets to work around bugs in
927 This means that flows between very close hosts can use bigger
938 to let TCP probe for bigger speeds, assuming cwnd can be
947 is applied to conservatively probe for bigger throughput.
|
| /openbmc/linux/Documentation/process/ |
| H A D | handling-regressions.rst | 165 * Work with the required care to avoid additional or bigger damage, even if
357 important unexpectedly comes up -- for example a bigger problem in the Linux
|
| H A D | coding-style.rst | 964 very often is not. Abundant use of the inline keyword leads to a much bigger
965 kernel, which in turn slows the system as a whole down, due to a bigger
|
| /openbmc/linux/arch/arm64/boot/dts/qcom/ |
| H A D | sdm845-cheza.dtsi | 298 * Our mpss_region is 8MB bigger than the default one and that conflicts
|
| /openbmc/linux/init/ |
| H A D | Kconfig | 323 size is about 10% bigger than gzip; however its speed
335 is about 8% bigger than LZO. But the decompression speed is
1048 be bigger than the corresponding clamping defined at task group level.
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | devlink-trap.rst | 216 - Traps packets that should have been routed by the device, but were bigger
|
| /openbmc/linux/Documentation/driver-api/dmaengine/ |
| H A D | provider.rst | 41 really efficient, you'll get several bigger transfers. This is done
|
| /openbmc/linux/Documentation/userspace-api/netlink/ |
| H A D | intro.rst | 526 size of the CPU architecture, whichever is bigger. Particular Netlink
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | memory-hotplug.rst | 441 memory in a way that huge pages in bigger
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | st.rst | 277 is to use bigger write() byte counts (e.g., tar -b 64).
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-fetching.rst | 139 this were not the case, there would be bigger issues to worry about.
|
| /openbmc/linux/drivers/spi/ |
| H A D | Kconfig | 329 of 128Mb (in general can be of bigger size).
|
| /openbmc/openbmc/meta-security/recipes-ids/suricata/files/ |
| H A D | suricata.yaml | 862 # as total of memory used by the ring. So set this to something bigger
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | usb.rst | 186 hardware do more work (bigger transfers, tracking protocol state, and so
|