Searched full:heavy (Results 1 – 25 of 473) sorted by relevance
12345678910>>...19
| /kernel/linux/linux-5.10/net/sched/ |
| 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 …]
|
| /kernel/linux/linux-6.6/net/sched/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/thermal/ |
| 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 {
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/thermal/ |
| D | nvidia,tegra124-soctherm.txt | 37 * throttle events: Sub-nodes must be named as "light" or "heavy".
123 * When the "heavy" cooling device triggered,
127 throttle_heavy: heavy {
177 * When the "heavy" cooling device triggered,
180 throttle_heavy: heavy {
|
| /kernel/linux/linux-6.6/include/linux/ |
| 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()
|
| D | stop_machine.h | 103 * interrupts. This is a very heavy lock, which is equivalent to
120 * This can be thought of as a very heavy write lock, equivalent to
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | stop_machine.h | 98 * interrupts. This is a very heavy lock, which is equivalent to
115 * This can be thought of as a very heavy write lock, equivalent to
|
| /kernel/linux/linux-6.6/kernel/rcu/ |
| 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.
|
| /kernel/linux/linux-5.10/Documentation/kbuild/ |
| D | Kconfig.select-break | 9 # currently a feature of kconfig, given select was designed to be heavy handed.
|
| /kernel/linux/linux-6.6/Documentation/kbuild/ |
| D | Kconfig.select-break | 9 # currently a feature of kconfig, given select was designed to be heavy handed.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/regulator/ |
| D | richtek,rt4831-regulator.yaml | 22 voltage drop from the heavy loading scenario. But it also make the power
|
| /kernel/linux/linux-6.6/tools/perf/Documentation/ |
| 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
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/freescale/fman/ |
| D | Kconfig | 22 FMAN DMA read or writes under heavy traffic load may cause FMAN
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/freescale/fman/ |
| D | Kconfig | 21 FMAN DMA read or writes under heavy traffic load may cause FMAN
|
| /kernel/linux/linux-5.10/arch/arc/include/asm/ |
| D | barrier.h | 34 * heavy weight as it flushes the pipeline as well.
|
| /kernel/linux/linux-6.6/arch/arc/include/asm/ |
| D | barrier.h | 34 * heavy weight as it flushes the pipeline as well.
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| 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
|
| /kernel/linux/linux-6.6/Documentation/core-api/ |
| 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
|
| /kernel/linux/linux-5.10/kernel/rcu/ |
| D | Kconfig | 197 This option also prevents heavy loads from blocking RCU
200 Say Y here if you are working with real-time apps or heavy loads
|
| /kernel/linux/linux-6.6/drivers/staging/ |
| D | Kconfig | 8 them. Please note that these drivers are under heavy
|
| /kernel/linux/linux-5.10/arch/x86/kernel/ |
| D | pci-iommu_table.c | 62 /* Heavy handed way..*/ in check_iommu_entries()
|
| /kernel/linux/linux-6.6/Documentation/isdn/ |
| D | credits.rst | 69 For heavy-duty-beta-testing with his BBS ;)
|
| /kernel/linux/linux-5.10/Documentation/isdn/ |
| D | credits.rst | 69 For heavy-duty-beta-testing with his BBS ;)
|
| /kernel/linux/linux-6.6/tools/include/uapi/linux/ |
| 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 */
|
| /kernel/linux/linux-5.10/tools/include/uapi/linux/ |
| D | pkt_sched.h | 917 /* Heavy-Hitter Filter */
937 __u32 hh_overlimit; /* number of times max heavy-hitters was hit */
938 __u32 hh_tot_count; /* number of captured heavy-hitters so far */
939 __u32 hh_cur_count; /* number of current heavy-hitters */
|
12345678910>>...19