Home
last modified time | relevance | path

Searched refs:bandwidths (Results 1 – 12 of 12) sorted by relevance

/linux/tools/testing/selftests/drivers/net/hw/
H A Ddevlink_rate_tc_bw.py377 bandwidths = run_bandwidth_test(cfg)
378 bw_data = calculate_bandwidth_percentages(bandwidths)
/linux/Documentation/driver-api/cxl/linux/
H A Daccess-coordinates.rst92 arrived for a region in order to recalculate the bandwidths with possible
139 is created to collect all the endpoint bandwidths via the
158 this point all the bandwidths are aggregated per each host bridge, which is
162 bandwidth from the Generic Port (GP). The bandwidths for the GP are retrieved
/linux/net/wireless/
H A Dpmsr.c20 if (!(rdev->wiphy.pmsr_capa->ftm.bandwidths & BIT(out->chandef.width))) { in pmsr_parse_ftm()
H A Dcore.c776 !wiphy->pmsr_capa->ftm.bandwidths)) in wiphy_register()
790 if (WARN_ON(wiphy->pmsr_capa->ftm.bandwidths & in wiphy_register()
H A Dnl80211.c2324 cap->ftm.bandwidths)) in nl80211_send_pmsr_ftm_capa()
/linux/Documentation/mm/
H A Dnuma.rst34 bandwidths than accesses to memory on other, remote cells. NUMA platforms
/linux/Documentation/scheduler/
H A Dsched-deadline.rst199 For each runqueue, the algorithm GRUB keeps track of two different bandwidths:
201 - Active bandwidth (running_bw): this is the sum of the bandwidths of all
604 can be created while the sum of their bandwidths stays below:
/linux/Documentation/admin-guide/sysctl/
H A Dnet.rst174 which require setting up classes and bandwidths. Note that physical multiqueue
/linux/Documentation/core-api/
H A Dworkqueue.rst476 are the read bandwidths and CPU utilizations depending on different affinity
/linux/include/net/
H A Dcfg80211.h5722 u32 bandwidths; member
/linux/drivers/net/wireless/intel/iwlwifi/mvm/
H A Dmac80211.c88 .bandwidths = BIT(NL80211_CHAN_WIDTH_20_NOHT) |
/linux/drivers/net/wireless/virtual/
H A Dmac80211_hwsim.c6301 out->ftm.bandwidths = nla_get_u32(tb[NL80211_PMSR_FTM_CAPA_ATTR_BANDWIDTHS]); in parse_ftm_capa()