| /linux-6.14.4/arch/arm64/boot/dts/microchip/ |
| D | sparx5_pcb135_board.dtsi | 366 microchip,bandwidth = <1000>;
373 microchip,bandwidth = <1000>;
380 microchip,bandwidth = <1000>;
387 microchip,bandwidth = <1000>;
394 microchip,bandwidth = <1000>;
401 microchip,bandwidth = <1000>;
408 microchip,bandwidth = <1000>;
415 microchip,bandwidth = <1000>;
422 microchip,bandwidth = <1000>;
429 microchip,bandwidth = <1000>;
[all …]
|
| /linux-6.14.4/sound/firewire/ |
| D | iso-resources.c | 55 /* convert to bandwidth units (quadlets at S1600 = bytes at S400) */ in packet_bandwidth()
69 * 88.3 + N * 24.3 in bandwidth units. in current_bandwidth_overhead()
91 * fw_iso_resources_allocate - allocate isochronous channel and bandwidth
96 * This function allocates one isochronous channel and enough bandwidth for the
109 int bandwidth, channel, err; in fw_iso_resources_allocate() local
114 r->bandwidth = packet_bandwidth(max_payload_bytes, speed); in fw_iso_resources_allocate()
128 bandwidth = r->bandwidth + r->bandwidth_overhead; in fw_iso_resources_allocate()
130 &channel, &bandwidth, true); in fw_iso_resources_allocate()
167 int bandwidth, channel; in fw_iso_resources_update() local
181 bandwidth = r->bandwidth + r->bandwidth_overhead; in fw_iso_resources_update()
[all …]
|
| /linux-6.14.4/drivers/firewire/ |
| D | core-iso.c | 5 * - Isochronous bus resource management (channels, bandwidth), client side
273 * Isochronous bus resource management (channels, bandwidth), client side
277 int bandwidth, bool allocate) in manage_bandwidth() argument
288 new = allocate ? old - bandwidth : old + bandwidth; in manage_bandwidth()
299 /* A generation change frees all bandwidth. */ in manage_bandwidth()
300 return allocate ? -EAGAIN : bandwidth; in manage_bandwidth()
304 return bandwidth; in manage_bandwidth()
380 * fw_iso_resource_manage() - Allocate or deallocate a channel and/or bandwidth
385 * @bandwidth: pointer for returning bandwidth allocation result
388 * In parameters: card, generation, channels_mask, bandwidth, allocate
[all …]
|
| /linux-6.14.4/Documentation/driver-api/cxl/ |
| D | access-coordinates.rst | 11 Root Ports (RP), there is the possibility of the total bandwidth for all
63 cxl_endpoint_gather_bandwidth() function. The min() of bandwidth from the
64 endpoint CDAT and the upstream link bandwidth is calculated. If the endpoint
65 has a CXL switch as a parent, then min() of calculated bandwidth and the
66 bandwidth from the SSLBIS for the switch downstream port that is associated
67 with the endpoint is calculated. The final bandwidth is stored in a
76 gathered bandwidth and the upstream link bandwidth. If there's a switch
84 The next step is to take the min() of the per host bridge bandwidth and the
85 bandwidth from the Generic Port (GP). The bandwidths for the GP is retrieved
86 via ACPI tables SRAT/HMAT. The min bandwidth are aggregated under the same
[all …]
|
| /linux-6.14.4/tools/testing/selftests/tc-testing/tc-tests/qdiscs/ |
| D | cake.json | 17 …"matchPattern": "qdisc cake 1: root refcnt [0-9]+ bandwidth unlimited diffserv3 triple-isolate non…
25 "name": "Create CAKE with bandwidth limit",
35 "cmdUnderTest": "$TC qdisc add dev $DUMMY handle 1: root cake bandwidth 1000",
38 …"matchPattern": "qdisc cake 1: root refcnt [0-9]+ bandwidth 1Kbit diffserv3 triple-isolate nonat n…
59 …"matchPattern": "qdisc cake 1: root refcnt [0-9]+ bandwidth unlimited autorate-ingress diffserv3 t…
80 …"matchPattern": "qdisc cake 1: root refcnt [0-9]+ bandwidth unlimited diffserv3 triple-isolate non…
101 …"matchPattern": "qdisc cake 1: root refcnt [0-9]+ bandwidth unlimited besteffort triple-isolate no…
122 …"matchPattern": "qdisc cake 1: root refcnt [0-9]+ bandwidth unlimited diffserv8 triple-isolate non…
143 …"matchPattern": "qdisc cake 1: root refcnt [0-9]+ bandwidth unlimited diffserv4 triple-isolate non…
164 …"matchPattern": "qdisc cake 1: root refcnt [0-9]+ bandwidth unlimited diffserv3 flowblind nonat no…
[all …]
|
| D | choke.json | 14 "cmdUnderTest": "$TC qdisc add dev $DUMMY handle 1: root choke limit 1000 bandwidth 10000",
35 …"cmdUnderTest": "$TC qdisc add dev $DUMMY handle 1: root choke limit 1000 bandwidth 10000 min 100",
56 …"cmdUnderTest": "$TC qdisc add dev $DUMMY handle 1: root choke limit 1000 bandwidth 10000 max 900",
77 … "cmdUnderTest": "$TC qdisc add dev $DUMMY handle 1: root choke limit 1000 bandwidth 10000 ecn",
98 …"cmdUnderTest": "$TC qdisc add dev $DUMMY handle 1: root choke limit 1000 bandwidth 10000 burst 10…
118 "$TC qdisc add dev $DUMMY handle 1: root choke limit 1000 bandwidth 10000"
139 "$TC qdisc add dev $DUMMY handle 1: root choke limit 1000 bandwidth 10000"
141 …"cmdUnderTest": "$TC qdisc replace dev $DUMMY handle 1: root choke limit 1000 bandwidth 10000 min …
161 "$TC qdisc add dev $DUMMY handle 1: root choke limit 1000 bandwidth 10000"
163 …"cmdUnderTest": "$TC qdisc change dev $DUMMY handle 1: root choke limit 1000 bandwidth 10000 min 1…
|
| /linux-6.14.4/drivers/usb/host/ |
| D | xhci-mtk.h | 28 * bandwidth to it.
37 * @fs_bus_bw_out: save bandwidth used by FS/LS OUT eps in each uframes
38 * @fs_bus_bw_in: save bandwidth used by FS/LS IN eps in each uframes
39 * @ls_bus_bw: save bandwidth used by LS eps in each uframes
40 * @fs_frame_bw: save bandwidth used by FS/LS eps in each FS frames
54 * struct mu3h_sch_bw_info: schedule information for bandwidth domain
56 * @bus_bw: array to keep track of bandwidth already used at each uframes
58 * treat a HS root port as a bandwidth domain, but treat a SS root port as
59 * two bandwidth domains, one for IN eps and another for OUT eps.
73 * @endpoint: linked into bandwidth domain which it belongs to
[all …]
|
| /linux-6.14.4/Documentation/scheduler/ |
| D | sched-bwc.rst | 2 CFS Bandwidth Control
6 This document only discusses CPU bandwidth control for SCHED_NORMAL.
9 CFS bandwidth control is a CONFIG_FAIR_GROUP_SCHED extension which allows the
10 specification of the maximum CPU bandwidth available to a group or hierarchy.
12 The bandwidth allowed for a group is specified using a quota and period. Within
21 cfs_quota units at each period boundary. As threads consume this bandwidth it
30 Traditional (UP-EDF) bandwidth control is something like:
89 bandwidth restriction in place, such a group is described as an unconstrained
90 bandwidth group. This represents the traditional work-conserving behavior for
94 enact the specified bandwidth limit. The minimum quota allowed for the quota or
[all …]
|
| D | sched-rt-group.rst | 43 the amount of bandwidth (eg. CPU time) being constant. In order to schedule
90 The scheduling period that is equivalent to 100% CPU bandwidth.
97 CONFIG_RT_GROUP_SCHED=y it also signifies the total bandwidth available to
106 bandwidth for fair dl_server. For accurate value check average of
119 By default all bandwidth is assigned to the root group and new groups get the
121 want to assign bandwidth to another group, reduce the root group's bandwidth
125 bandwidth to the group before it will accept real-time tasks. Therefore you will
135 CPU bandwidth to task groups.
163 Consider two sibling groups A and B; both have 50% bandwidth, but A's
|
| D | sched-deadline.rst | 11 2.2 Bandwidth reclaiming
17 4. Bandwidth management
42 algorithm, augmented with a mechanism (called Constant Bandwidth Server, CBS)
62 "admission control" strategy (see Section "4. Bandwidth management") is used
67 interference between different tasks (bandwidth isolation), while the EDF[1]
125 2.2 Bandwidth reclaiming
128 Bandwidth reclaiming for deadline tasks is based on the GRUB (Greedy
129 Reclamation of Unused Bandwidth) algorithm [15, 16, 17] and it is enabled
164 bandwidth cannot be immediately reclaimed without breaking the
167 the 0-lag time, when the task's bandwidth can be reclaimed without
[all …]
|
| /linux-6.14.4/drivers/net/ethernet/intel/ixgbe/ |
| D | ixgbe_dcb.h | 26 /* Error in bandwidth group allocation */
28 /* Error in traffic class bandwidth allocation */
32 /* Link strict traffic class has non zero bandwidth */
34 /* Link strict bandwidth group has non zero bandwidth */
36 /* Traffic class has zero bandwidth */
73 /* Traffic class bandwidth allocation per direction */
75 u8 bwg_id; /* Bandwidth Group (BWG) ID */
76 u8 bwg_percent; /* % of BWG's bandwidth */
77 u8 link_percent; /* % of link bandwidth */
114 u32 link_speed; /* For bandwidth allocation validation purpose */
|
| /linux-6.14.4/drivers/cxl/core/ |
| D | cdat.c | 36 * Scoped Latency and Bandwidth Information Structure in Coherent Device in cdat_normalize()
598 * Transient context for containing the current calculation of bandwidth when
607 * cxl_endpoint_gather_bandwidth - collect all the endpoint bandwidth in an xarray
608 * @cxlr: CXL region for the bandwidth calculation
610 * @usp_xa: (output) the xarray that collects all the bandwidth coordinates
616 * Collects aggregated endpoint bandwidth and store the bandwidth in
618 * device. Each endpoint consists the minimum of the bandwidth from DSLBIS
619 * from the endpoint CDAT, the endpoint upstream link bandwidth, and the
620 * bandwidth from the SSLBIS of the switch CDAT for the switch upstream port to
680 /* Direct upstream link from EP bandwidth */ in cxl_endpoint_gather_bandwidth()
[all …]
|
| /linux-6.14.4/Documentation/admin-guide/perf/ |
| D | hisi-pcie-pmu.rst | 6 bandwidth, latency, bus utilization and buffer occupancy data of PCIe.
45 The related events usually used to calculate the bandwidth, latency or others.
51 bandwidth events "xxx_flux, xxx_time".
93 "bdf" filter can only be used in bandwidth events, target Endpoint is
94 selected by configuring BDF to "bdf". Counter only counts the bandwidth of
108 only be used in bandwidth events.
122 "thr_mode". This filter can only be used in bandwidth events.
134 When counting bandwidth, the data can be composed of certain parts of TLP
138 - 2'b01: Bandwidth of TLP payloads
139 - 2'b10: Bandwidth of TLP headers
[all …]
|
| D | alibaba_pmu.rst | 30 - Group 1: PMU Bandwidth Counters. This group has 8 counters that are used
54 interface, we could calculate the bandwidth. Example usage of counting memory
55 data bandwidth::
91 Example usage of counting all memory read/write bandwidth by metric::
96 The average DRAM bandwidth can be calculated as follows:
98 - Read Bandwidth = perf_hif_rd * DDRC_WIDTH * DDRC_Freq / DDRC_Cycle
99 - Write Bandwidth = (perf_hif_wr + perf_hif_rmw) * DDRC_WIDTH * DDRC_Freq / DDRC_Cycle
|
| /linux-6.14.4/net/mac80211/ |
| D | wbrf.c | 28 static void get_chan_freq_boundary(u32 center_freq, u32 bandwidth, u64 *start, u64 *end) in get_chan_freq_boundary() argument
30 bandwidth *= KHZ_PER_MHZ; in get_chan_freq_boundary()
33 *start = center_freq - bandwidth / 2; in get_chan_freq_boundary()
34 *end = center_freq + bandwidth / 2; in get_chan_freq_boundary()
46 int bandwidth; in get_ranges_from_chandef() local
48 bandwidth = nl80211_chan_width_to_mhz(chandef->width); in get_ranges_from_chandef()
50 get_chan_freq_boundary(chandef->center_freq1, bandwidth, &start_freq1, &end_freq1); in get_ranges_from_chandef()
57 get_chan_freq_boundary(chandef->center_freq2, bandwidth, &start_freq2, &end_freq2); in get_ranges_from_chandef()
|
| /linux-6.14.4/drivers/thunderbolt/ |
| D | tb.c | 23 * How many time bandwidth allocation request from graphics driver is
29 * Minimum bandwidth (in Mb/s) that is needed in the single transmitter/receiver
30 * direction. This is 40G - 10% guard band bandwidth.
35 * Threshold bandwidth (in Mb/s) that is used to switch the links to
62 * @groups: Bandwidth groups used in this domain.
540 * tb_consumed_usb3_pcie_bandwidth() - Consumed USB3/PCIe bandwidth over a single link
544 * @port: USB4 port the consumed bandwidth is calculated
545 * @consumed_up: Consumed upsream bandwidth (Mb/s)
546 * @consumed_down: Consumed downstream bandwidth (Mb/s)
548 * Calculates consumed USB3 and PCIe bandwidth at @port between path
[all …]
|
| D | tunnel.h | 49 * @maximum_bandwidth: Returns maximum possible bandwidth for this tunnel
50 * @allocated_bandwidth: Return how much bandwidth is allocated for the tunnel
51 * @alloc_bandwidth: Change tunnel bandwidth allocation
52 * @consumed_bandwidth: Return how much bandwidth the tunnel consumes
53 * @release_unused_bandwidth: Release all unused bandwidth
54 * @reclaim_available_bandwidth: Reclaim back available bandwidth
58 * @max_up: Maximum upstream bandwidth (Mb/s) available for the tunnel.
59 * Only set if the bandwidth needs to be limited.
60 * @max_down: Maximum downstream bandwidth (Mb/s) available for the tunnel.
61 * Only set if the bandwidth needs to be limited.
[all …]
|
| D | tunnel.c | 65 * Reserve additional bandwidth for USB 3.x and PCIe bulk traffic
99 "enable bandwidth allocation mode if supported (default: true)");
465 * tb_tunnel_reserved_pci() - Amount of bandwidth to reserve for PCIe
467 * @reserved_up: Upstream bandwidth in Mb/s to reserve
468 * @reserved_down: Downstream bandwidth in Mb/s to reserve
471 * bandwidth needs to be left in reserve for possible PCIe bulk traffic.
748 "DP IN maximum supported bandwidth %u Mb/s x%u = %u Mb/s\n", in tb_dp_xchg_caps()
752 * If the tunnel bandwidth is limited (max_bw is set) then see in tb_dp_xchg_caps()
753 * if we need to reduce bandwidth to fit there. in tb_dp_xchg_caps()
759 "DP OUT maximum supported bandwidth %u Mb/s x%u = %u Mb/s\n", in tb_dp_xchg_caps()
[all …]
|
| /linux-6.14.4/Documentation/arch/x86/ |
| D | resctrl.rst | 25 MBM (Memory Bandwidth Monitoring) "cqm_mbm_total", "cqm_mbm_local"
26 MBA (Memory Bandwidth Allocation) "mba"
27 SMBA (Slow Memory Bandwidth Allocation) ""
28 BMEC (Bandwidth Monitoring Event Configuration) ""
48 bandwidth in MiBps
138 Memory bandwidth(MB) subdirectory contains the following files
142 The minimum memory bandwidth percentage which
146 The granularity in which the memory bandwidth
150 available bandwidth control steps are:
161 request different memory bandwidth percentages:
[all …]
|
| /linux-6.14.4/drivers/gpu/drm/bridge/ |
| D | cros-ec-anx7688.c | 61 /* Read both regs 0x85 (bandwidth) and 0x86 (lane count). */ in cros_ec_anx7688_bridge_mode_fixup()
64 DRM_ERROR("Failed to read bandwidth/lane count\n"); in cros_ec_anx7688_bridge_mode_fixup()
70 /* Maximum 0x19 bandwidth (6.75 Gbps Turbo mode), 2 lanes */ in cros_ec_anx7688_bridge_mode_fixup()
72 DRM_ERROR("Invalid bandwidth/lane count (%02x/%d)\n", dpbw, in cros_ec_anx7688_bridge_mode_fixup()
77 /* Compute available bandwidth (kHz) */ in cros_ec_anx7688_bridge_mode_fixup()
80 /* Required bandwidth (8 bpc, kHz) */ in cros_ec_anx7688_bridge_mode_fixup()
83 DRM_DEBUG_KMS("DP bandwidth: %d kHz (%02x/%d); mode requires %d Khz\n", in cros_ec_anx7688_bridge_mode_fixup()
87 DRM_ERROR("Bandwidth/lane count are 0, not rejecting modes\n"); in cros_ec_anx7688_bridge_mode_fixup()
148 /* FW version >= 0.85 supports bandwidth/lane count registers */ in cros_ec_anx7688_bridge_probe()
|
| /linux-6.14.4/tools/perf/pmu-events/arch/x86/amdzen5/ |
| D | recommended.json | 307 "BriefDescription": "Estimated memory read bandwidth.",
315 "BriefDescription": "Estimated memory write bandwidth.",
323 "BriefDescription": "Estimated combined memory bandwidth.",
347 "BriefDescription": "DRAM read data bandwidth for accesses in local or remote socket.",
355 "BriefDescription": "DRAM write data bandwidth for accesses in local socket.",
363 "BriefDescription": "DRAM write data bandwidth for accesses in remote socket.",
371 "BriefDescription": "DRAM write data bandwidth for accesses in local or remote socket.",
379 "BriefDescription": "Upstream DMA read data bandwidth for accesses in local socket.",
387 "BriefDescription": "Upstream DMA write data bandwidth for accesses in local socket.",
395 "BriefDescription": "Upstream DMA read data bandwidth for accesses in remote socket.",
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/powerpc/power9/ |
| D | nest_metrics.json | 31 "MetricGroup" : "memory-bandwidth",
37 "MetricGroup" : "memory-bandwidth",
43 "MetricGroup" : "memory-bandwidth",
49 "MetricGroup" : "memory-bandwidth",
59 "MetricName" : "Memory-bandwidth-MCS",
60 "MetricGroup" : "memory-bandwidth",
|
| /linux-6.14.4/drivers/media/tuners/ |
| D | si2157.c | 450 u32 bandwidth; in si2157_set_params() local
463 bandwidth = 1700000; in si2157_set_params()
466 bandwidth = 6000000; in si2157_set_params()
469 bandwidth = 6100000; in si2157_set_params()
472 bandwidth = 7000000; in si2157_set_params()
475 bandwidth = 8000000; in si2157_set_params()
555 dev->bandwidth = bandwidth; in si2157_set_params()
562 dev->bandwidth = 0; in si2157_set_params()
577 u32 bandwidth = 0; in si2157_set_analog_params() local
602 * bandwidth = 1700000; //best can do for FM, AGC will be a mess though in si2157_set_analog_params()
[all …]
|
| /linux-6.14.4/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | uncore-interconnect.json | 407 …nes, decreasing our bandwidth in order to save power. It increases snoop and data transfer latenc…
532 …bandwidth of the link by taking: flits*80b/time. Note that this is not the same as 'data' bandwid…
542 …bandwidth of the link by taking: flits*80b/time. Note that this is not the same as 'data' bandwid…
552 …bandwidth of the link by taking: flits*80b/time. Note that this is not the same as 'data' bandwid…
562 …bandwidth of the link by taking: flits*80b/time. Note that this is not the same as 'data' bandwid…
572 …bandwidth of the link by taking: flits*80b/time. Note that this is not the same as 'data' bandwid…
582 …bandwidth of the link by taking: flits*80b/time. Note that this is not the same as 'data' bandwid…
592 …bandwidth of the link by taking: flits*80b/time. Note that this is not the same as 'data' bandwid…
602 …bandwidth of the link by taking: flits*80b/time. Note that this is not the same as 'data' bandwid…
612 …bandwidth of the link by taking: flits*80b/time. Note that this is not the same as 'data' bandwid…
[all …]
|
| /linux-6.14.4/Documentation/devicetree/bindings/net/ |
| D | microchip,sparx5-switch.yaml | 118 microchip,bandwidth:
119 description: Specifies bandwidth in Mbit/s allocated to the port.
154 - microchip,bandwidth
192 microchip,bandwidth = <1000>;
201 microchip,bandwidth = <25000>;
210 microchip,bandwidth = <25000>;
219 microchip,bandwidth = <25000>;
228 microchip,bandwidth = <25000>;
238 microchip,bandwidth = <1000>;
|