Home
last modified time | relevance | path

Searched refs:tracker (Results 1 – 17 of 17) sorted by relevance

/Linux-v5.15/drivers/net/ethernet/mellanox/mlx5/core/
Dlag_mp.c53 struct lag_tracker tracker; in mlx5_lag_set_port_affinity() local
60 tracker.netdev_state[MLX5_LAG_P1].tx_enabled = true; in mlx5_lag_set_port_affinity()
61 tracker.netdev_state[MLX5_LAG_P2].tx_enabled = true; in mlx5_lag_set_port_affinity()
62 tracker.netdev_state[MLX5_LAG_P1].link_up = true; in mlx5_lag_set_port_affinity()
63 tracker.netdev_state[MLX5_LAG_P2].link_up = true; in mlx5_lag_set_port_affinity()
66 tracker.netdev_state[MLX5_LAG_P1].tx_enabled = true; in mlx5_lag_set_port_affinity()
67 tracker.netdev_state[MLX5_LAG_P1].link_up = true; in mlx5_lag_set_port_affinity()
68 tracker.netdev_state[MLX5_LAG_P2].tx_enabled = false; in mlx5_lag_set_port_affinity()
69 tracker.netdev_state[MLX5_LAG_P2].link_up = false; in mlx5_lag_set_port_affinity()
72 tracker.netdev_state[MLX5_LAG_P1].tx_enabled = false; in mlx5_lag_set_port_affinity()
[all …]
Dlag.c179 static void mlx5_infer_tx_affinity_mapping(struct lag_tracker *tracker, in mlx5_infer_tx_affinity_mapping() argument
185 p1en = tracker->netdev_state[MLX5_LAG_P1].tx_enabled && in mlx5_infer_tx_affinity_mapping()
186 tracker->netdev_state[MLX5_LAG_P1].link_up; in mlx5_infer_tx_affinity_mapping()
188 p2en = tracker->netdev_state[MLX5_LAG_P2].tx_enabled && in mlx5_infer_tx_affinity_mapping()
189 tracker->netdev_state[MLX5_LAG_P2].link_up; in mlx5_infer_tx_affinity_mapping()
203 struct lag_tracker *tracker) in mlx5_modify_lag() argument
209 mlx5_infer_tx_affinity_mapping(tracker, &v2p_port1, in mlx5_modify_lag()
230 struct lag_tracker *tracker, in mlx5_create_lag() argument
238 mlx5_infer_tx_affinity_mapping(tracker, &ldev->v2p_map[MLX5_LAG_P1], in mlx5_create_lag()
274 struct lag_tracker *tracker, in mlx5_activate_lag() argument
[all …]
Dlag.h47 struct lag_tracker tracker; member
73 struct lag_tracker *tracker);
75 struct lag_tracker *tracker,
/Linux-v5.15/drivers/net/ethernet/mellanox/mlx4/
Dresource_tracker.c1003 struct mlx4_resource_tracker *tracker = &priv->mfunc.master.res_tracker; in handle_unexisting_counter() local
1011 &tracker->slave_list[slave].res_list[RES_COUNTER], in handle_unexisting_counter()
1235 struct mlx4_resource_tracker *tracker = &priv->mfunc.master.res_tracker; in mlx4_calc_vf_counters() local
1250 &tracker->slave_list[slave].res_list[RES_COUNTER], in mlx4_calc_vf_counters()
1285 struct mlx4_resource_tracker *tracker = &priv->mfunc.master.res_tracker; in add_res_range() local
1286 struct rb_root *root = &tracker->res_tree[type]; in add_res_range()
1313 &tracker->slave_list[slave].res_list[type]); in add_res_range()
1471 struct mlx4_resource_tracker *tracker = &priv->mfunc.master.res_tracker; in rem_res_range() local
1476 r = res_tracker_lookup(&tracker->res_tree[type], i); in rem_res_range()
1491 r = res_tracker_lookup(&tracker->res_tree[type], i); in rem_res_range()
[all …]
/Linux-v5.15/Documentation/core-api/
Ddebug-objects.rst83 allocates a tracker object for the real object and sets the tracker
106 allocates a tracker object for the real object and sets the tracker
110 An object which is on the stack must be removed from the tracker by
136 tracker object is set to ODEBUG_STATE_ACTIVE.
150 tracker object is set to ODEBUG_STATE_INACTIVE.
169 tracker object is set to ODEBUG_STATE_DESTROYED.
184 Note that debug_object_free removes the object from the tracker. Later
215 object and the state which is currently recorded in the tracker.
253 to make the object known to the tracker and marked active. In this case
304 should be called to make the object known to the tracker. Then the
/Linux-v5.15/drivers/virt/vboxguest/
Dvboxguest_core.c502 static bool vbg_track_bit_usage(struct vbg_bit_usage_tracker *tracker, in vbg_track_bit_usage() argument
512 tracker->per_bit_usage[bit] -= 1; in vbg_track_bit_usage()
513 if (tracker->per_bit_usage[bit] == 0) { in vbg_track_bit_usage()
515 tracker->mask &= ~bitmask; in vbg_track_bit_usage()
518 tracker->per_bit_usage[bit] += 1; in vbg_track_bit_usage()
519 if (tracker->per_bit_usage[bit] == 1) { in vbg_track_bit_usage()
521 tracker->mask |= bitmask; in vbg_track_bit_usage()
/Linux-v5.15/Documentation/driver-api/thermal/
Dnouveau_thermal.rst95 Bug reports should be filled on Freedesktop's bug tracker. Please follow
/Linux-v5.15/drivers/md/
DMakefile22 dm-cache-background-tracker.o
Ddm-cache-target.c403 struct dm_io_tracker tracker; member
799 dm_iot_io_begin(&cache->tracker, pb->len); in accounted_begin()
807 dm_iot_io_end(&cache->tracker, pb->len); in accounted_complete()
1575 bool idle = dm_iot_idle_for(&cache->tracker, HZ); in spare_migration_bandwidth()
2536 dm_iot_init(&cache->tracker); in cache_create()
2758 WARN_ON(cache->tracker.in_flight); in cache_postsuspend()
/Linux-v5.15/Documentation/kbuild/
Dllvm.rst98 yet. Bug reports are always welcome at the issue tracker below!
/Linux-v5.15/Documentation/admin-guide/
Dreporting-issues.rst119 * Search the archives of the bug tracker or mailing list in question
620 Problem is: the Linux kernel lacks a central bug tracker where you can simply
693 you where to find a subsystem specific bug tracker to file your issue. The
696 a bug tracker, and only some of those rely on bugzilla.kernel.org.
751 *Search the archives of the bug tracker or mailing list in question
774 at this point. If your report needs to be filed in a bug tracker, you may want
1152 your report. If you are filing the issue in a bug tracker then attach them to
1257 tracker, proceed to do so. Once filed, forward the report by mail to the
1275 * If you were supposed to file the issue in a bug tracker make sure to mark
1276 the ticket as 'private' or 'security issue'. If the bug tracker does not
[all …]
Ddevices.txt2552 190 char Kansas City tracker/tuner card
/Linux-v5.15/Documentation/networking/
Dgtp.rst141 The Osmocom project maintains an issue tracker for the Kernel GTP-U
/Linux-v5.15/drivers/usb/serial/
DKconfig581 tristate "Xsens motion tracker serial interface driver"
/Linux-v5.15/drivers/perf/
Dxgene_pmu.c572 XGENE_PMU_EVENT_ATTR(tmaw-tracker-full, 0x2c),
/Linux-v5.15/Documentation/bpf/
Dbpf_devel_QA.rst561 LLVM also has an issue tracker where BPF related bugs can be found:
/Linux-v5.15/
DMAINTAINERS100 filing info, a direct bug tracker link, or a mailto: URI.