| /openbmc/linux/net/sched/ |
| H A D | sch_hhf.c | 2 /* net/sched/sch_hhf.c Heavy-Hitter Filter (HHF)
16 /* Heavy-Hitter Filter (HHF)
19 * Flows are classified into two buckets: non-heavy-hitter and heavy-hitter
20 * buckets. Initially, a new flow starts as non-heavy-hitter. Once classified
21 * as heavy-hitter, it is immediately switched to the heavy-hitter bucket.
23 * in which the heavy-hitter bucket is served with less weight.
24 * In other words, non-heavy-hitters (e.g., short bursts of critical traffic)
25 * are isolated from heavy-hitters (e.g., persistent bulk traffic) and also have
28 * To capture heavy-hitters, we use the "multi-stage filter" algorithm in the
37 * - For a heavy-hitter flow: *all* of its k array counters must be large.
[all …]
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/fans/phosphor-fan-control-zone-config/witherspoon/ |
| H A D | zones.yaml | 36 Heavy IO thermal control mode for handling the use
37 of PCI cards that produce heavy IO utilization and
84 Heavy IO thermal control mode for handling the use
85 of PCI cards that produce heavy IO utilization and
|
| /openbmc/linux/Documentation/devicetree/bindings/thermal/ |
| H A D | nvidia,tegra124-soctherm.yaml | 66 Throttle event sub-nodes must be named as "light" or "heavy".
69 "^(light|heavy|oc1)$":
259 * When the "heavy" cooling device triggered,
263 heavy {
321 * When the "heavy" cooling device triggered,
324 heavy {
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/python3/ |
| H A D | 0001-skip-no_stdout_fileno-test-due-to-load-variability.patch | 7 under heavy load.
26 + @unittest.skip("Test may fail under heavy load")
|
| H A D | 0001-test_storlines-skip-due-to-load-variability.patch | 7 a worker is under heavy load, so skip it during testing.
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-extended/tgt/ |
| H A D | tgt_1.0.90.bb | 69 perl-module-exporter-heavy \
73 perl-module-carp-heavy \
|
| /openbmc/linux/include/linux/ |
| H A D | freelist.h | 11 * under heavy contention, but simple and correct (assuming nodes are never
38 * heavy contention, when the refcount goes to zero in between a load in __freelist_add()
|
| H A D | stop_machine.h | 92 * interrupts. This is a very heavy lock, which is equivalent to
109 * This can be thought of as a very heavy write lock, equivalent to
|
| /openbmc/linux/kernel/rcu/ |
| H A D | Kconfig | 201 This option also prevents heavy loads from blocking RCU
204 Say Y here if you are working with real-time apps or heavy loads
281 to avoid starvation by heavy SCHED_OTHER background load.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-benchmark/tiobench/ |
| H A D | tiobench_0.3.3.bb | 24 perl-module-exporter-heavy \
|
| /openbmc/openbmc/poky/meta/recipes-extended/diffutils/diffutils/ |
| H A D | 0001-Skip-strip-trailing-cr-test-case.patch | 7 work, but valgrind is considered too heavy-weight for diffutils
|
| /openbmc/linux/Documentation/kbuild/ |
| H A D | Kconfig.select-break | 9 # currently a feature of kconfig, given select was designed to be heavy handed.
|
| /openbmc/linux/Documentation/devicetree/bindings/regulator/ |
| H A D | richtek,rt4831-regulator.yaml | 22 voltage drop from the heavy loading scenario. But it also make the power
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | topdown.txt | 8 heavy operations, light operations, branch mispredicts, machine
254 printf("Heavy Operations %.2f%% Light Operations %.2f%% "
316 topdown-heavy-ops, topdown-br-mispredict, topdown-fetch-lat and
|
| /openbmc/linux/drivers/net/ethernet/freescale/fman/ |
| H A D | Kconfig | 22 FMAN DMA read or writes under heavy traffic load may cause FMAN
|
| /openbmc/linux/arch/arc/include/asm/ |
| H A D | barrier.h | 34 * heavy weight as it flushes the pipeline as well.
|
| /openbmc/openbmc/poky/meta/recipes-support/libevent/libevent/ |
| H A D | 0002-test-regress.h-Increase-default-timeval-tolerance-50.patch | 12 (The root cause seems to be a heavy load)
|
| /openbmc/openbmc/poky/meta/recipes-devtools/rust/files/ |
| H A D | oeqa-selftest-Increase-timeout-in-process-sigpipe-ru.patch | 7 occasionally fails when the server is under heavy load. Increasing the timeout
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | errseq.rst | 50 overall, but the company is a little...management heavy. He has to
100 glitches and he makes a mistake. He sighs a heavy sigh, and marks it
|
| /openbmc/linux/drivers/staging/ |
| H A D | Kconfig | 8 them. Please note that these drivers are under heavy
|
| /openbmc/openbmc/poky/meta/recipes-core/images/ |
| H A D | core-image-tiny-initramfs.bb | 10 # however this keeps the image small by not installing heavy-weight manager and in initramfs it may…
|
| /openbmc/linux/Documentation/isdn/ |
| H A D | credits.rst | 69 For heavy-duty-beta-testing with his BBS ;)
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/perl/ |
| H A D | libdbi-perl_1.646.bb | 38 perl-module-exporter-heavy \
|
| /openbmc/linux/tools/include/uapi/linux/ |
| H A D | pkt_sched.h | 918 /* Heavy-Hitter Filter */
938 __u32 hh_overlimit; /* number of times max heavy-hitters was hit */
939 __u32 hh_tot_count; /* number of captured heavy-hitters so far */
940 __u32 hh_cur_count; /* number of current heavy-hitters */
|
| /openbmc/linux/fs/ubifs/ |
| H A D | Kconfig | 62 strictatime is the "heavy", relatime is "lighter", etc.
|