Expose error burst period for devlink health reporter
Subsystems (16)
Tariq Toukan
maintainerv3 cover Expose error burst period for devlink health reporter
Hi,
This series by Shahar implements error burst period in devlink health reporter, and use it in mlx5e driver.
This is V3. Find previous versions here:
https://lore.kernel.org/all/[email protected]/
https://lore.kernel.org/all/[email protected]/
See detailed feature description by Shahar below [1].
Regards,
Tariq
V3:
- Rebase.
- Rename feature: graceful period delay -> error burst period.
[1]
Currently, the devlink health reporter initiates the grace period immediately after recovering an error, which blocks further recovery attempts until the grace period concludes. Since additional errors are not generally expected during this short interval, any new error reported during the grace period is not only rejected but also causes the reporter to enter an error state that requires manual intervention.
This approach poses a problem in scenarios where a single root cause triggers multiple related errors in quick succession - for example, a PCI issue affecting multiple hardware queues. Because these errors are closely related and occur rapidly, it is more effective to handle them together rather than handling only the first one reported and blocking any subsequent recovery attempts. Furthermore, setting the reporter to an error state in this context can be misleading, as these multiple errors are manifestations of a single underlying issue, making it unlike the general case where additional errors are not expected during the grace period.
To resolve this, introduce a configurable error burst period attribute to the devlink health reporter. This period starts when the first error is recovered and lasts for a user-defined duration. Once this error burst period expires, the grace period begins. After the grace period ends, a new reported error will start the same flow again.
Timeline summary:
----|--------|------------------------------/----------------------/--
error is error is error burst period grace period
reported recovered (recoveries allowed) (recoveries blocked)
With error burst period, create a time window during which recovery attempts are permitted, allowing all reported errors to be handled sequentially before the grace period starts. Once the grace period begins, it prevents any further error recoveries until it ends.
When error burst period is set to 0, current behavior is preserved.
Design alternatives considered:
1. Recover all queues upon any error:
A brute-force approach that recovers all queues on any error. While simple, it is overly aggressive and disrupts unaffected queues unnecessarily. Also, because this is handled entirely within the driver, it leads to a driver-specific implementation rather than a generic one.
2. Per-queue reporter:
This design would isolate recovery handling per SQ or RQ, effectively removing inter-dependencies between queues. While conceptually clean, it introduces significant scalability challenges as the number of queues grows, as well as synchronization challenges across multiple reporters.
3. Error aggregation with delayed handling:
Errors arriving during the grace period are saved and processed after it ends. While addressing the issue of related errors whose recovery is aborted as grace period started, this adds complexity due to synchronization needs and contradicts the assumption that no errors should occur during a healthy system’s grace period. Also, this breaks the important role of grace period in preventing an infinite loop of immediate error detection following recovery. In such cases we want to stop.
4. Allowing a fixed burst of errors before starting grace period:
Allows a set number of recoveries before the grace period begins. However, it also requires limiting the error reporting window. To keep the design simple, the burst threshold becomes redundant.
The error burst period design was chosen for its simplicity and precision in addressing the problem at hand. It effectively captures the temporal correlation of related errors and aligns with the original intent of the grace period as a stabilization window where further errors are unexpected, and if they do occur, they indicate an abnormal system state.
Shahar Shitrit (5):
devlink: Move graceful period parameter to reporter ops
devlink: Move health reporter recovery abort logic to a separate
function
devlink: Introduce error burst period for health reporter
devlink: Make health reporter error burst period configurable net/mlx5e: Set default error burst period for TX and RX reporters
Documentation/netlink/specs/devlink.yaml | 6 + .../networking/devlink/devlink-health.rst | 2 +- drivers/net/ethernet/amd/pds_core/main.c | 2 +- .../net/ethernet/broadcom/bnxt/bnxt_devlink.c | 2 +- .../net/ethernet/huawei/hinic/hinic_devlink.c | 10 +- .../net/ethernet/intel/ice/devlink/health.c | 3 +- .../marvell/octeontx2/af/rvu_devlink.c | 32 +++-- .../mellanox/mlx5/core/diag/reporter_vnic.c | 2 +- .../mellanox/mlx5/core/en/reporter_rx.c | 12 +- .../mellanox/mlx5/core/en/reporter_tx.c | 13 ++- .../net/ethernet/mellanox/mlx5/core/en_rep.c | 2 +- .../net/ethernet/mellanox/mlx5/core/health.c | 41 ++++--- drivers/net/ethernet/mellanox/mlxsw/core.c | 2 +- drivers/net/ethernet/qlogic/qed/qed_devlink.c | 10 +- drivers/net/netdevsim/health.c | 4 +- include/net/devlink.h | 15 ++- include/uapi/linux/devlink.h | 2 + net/devlink/health.c | 109 +++++++++++++----- net/devlink/netlink_gen.c | 5 +- 19 files changed, 189 insertions(+), 85 deletions(-)
base-commit: fdbe93b7f0f86c943351ceab26c8fad548869f91
Signature · 1 line
2.31.1
Tariq Toukan
maintainerPATCH v3 1/5 devlink: Move graceful period parameter to reporter ops
From: Shahar Shitrit <[email protected]>
Move the default graceful period from a parameter to devlink_health_reporter_create() to a field in the devlink_health_reporter_ops structure.
This change improves consistency, as the graceful period is inherently tied to the reporter's behavior and recovery policy. It simplifies the signature of devlink_health_reporter_create() and its internal helper functions. It also centralizes the reporter configuration at the ops structure, preparing the groundwork for a downstream patch that will introduce a devlink health reporter error burst period attribute whose default value will similarly be provided by the driver via the ops structure.
--- drivers/net/ethernet/amd/pds_core/main.c | 2 +- .../net/ethernet/broadcom/bnxt/bnxt_devlink.c | 2 +- .../net/ethernet/huawei/hinic/hinic_devlink.c | 10 +++-- .../net/ethernet/intel/ice/devlink/health.c | 3 +- .../marvell/octeontx2/af/rvu_devlink.c | 32 +++++++++++---- .../mellanox/mlx5/core/diag/reporter_vnic.c | 2 +- .../mellanox/mlx5/core/en/reporter_rx.c | 10 +++-- .../mellanox/mlx5/core/en/reporter_tx.c | 10 +++-- .../net/ethernet/mellanox/mlx5/core/en_rep.c | 2 +- .../net/ethernet/mellanox/mlx5/core/health.c | 41 +++++++++++-------- drivers/net/ethernet/mellanox/mlxsw/core.c | 2 +- drivers/net/ethernet/qlogic/qed/qed_devlink.c | 10 +++-- drivers/net/netdevsim/health.c | 4 +- include/net/devlink.h | 11 +++-- net/devlink/health.c | 28 +++++-------- 15 files changed, 98 insertions(+), 71 deletions(-)
drivers/net/ethernet/amd/pds_core/main.c +1 -1
@@ -280,7 +280,7 @@ static int pdsc_init_pf(struct pdsc *pdsc) goto err_out_del_dev; } - hr =devl_health_reporter_create (dl, &pdsc_fw_reporter_ops,0 , pdsc); + hr =devl_health_reporter_create (dl, &pdsc_fw_reporter_ops, pdsc);if (IS_ERR (hr)) {devl_unlock (dl);dev_warn (pdsc->dev,"Failed to create fw reporter: %pe\n" , hr);
drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c +1 -1
@@ -220,7 +220,7 @@ __bnxt_dl_reporter_create(struct bnxt *bp, {struct devlink_health_reporter *reporter; - reporter =devlink_health_reporter_create (bp->dl, ops,0 , bp); + reporter =devlink_health_reporter_create (bp->dl, ops, bp);if (IS_ERR (reporter)) {netdev_warn (bp->dev,"Failed to create %s health reporter, rc = %ld\n" , ops->name,PTR_ERR (reporter));
drivers/net/ethernet/huawei/hinic/hinic_devlink.c +6 -4
@@ -443,8 +443,9 @@ int hinic_health_reporters_create(struct hinic_devlink_priv *priv)struct devlink *devlink =priv_to_devlink (priv); priv->hw_fault_reporter = -devlink_health_reporter_create (devlink, &hinic_hw_fault_reporter_ops, -0 , priv); +devlink_health_reporter_create (devlink, + &hinic_hw_fault_reporter_ops, + priv);if (IS_ERR (priv->hw_fault_reporter)) {dev_warn (&priv->hwdev->hwif->pdev->dev,"Failed to create hw fault reporter, err: %ld\n" ,PTR_ERR (priv->hw_fault_reporter));
@@ -452,8 +453,9 @@ int hinic_health_reporters_create(struct hinic_devlink_priv *priv) } priv->fw_fault_reporter = -devlink_health_reporter_create (devlink, &hinic_fw_fault_reporter_ops, -0 , priv); +devlink_health_reporter_create (devlink, + &hinic_fw_fault_reporter_ops, + priv);if (IS_ERR (priv->fw_fault_reporter)) {dev_warn (&priv->hwdev->hwif->pdev->dev,"Failed to create fw fault reporter, err: %ld\n" ,PTR_ERR (priv->fw_fault_reporter));
drivers/net/ethernet/intel/ice/devlink/health.c +1 -2
@@ -450,9 +450,8 @@ ice_init_devlink_rep(struct ice_pf *pf, {struct devlink *devlink =priv_to_devlink (pf);struct devlink_health_reporter *rep; -const u64 graceful_period =0 ; - rep =devl_health_reporter_create (devlink, ops, graceful_period, pf); + rep =devl_health_reporter_create (devlink, ops, pf);if (IS_ERR (rep)) {struct device *dev =ice_pf_to_dev (pf);
drivers/net/ethernet/marvell/octeontx2/af/rvu_devlink.c +24 -8
@@ -505,7 +505,9 @@ static int rvu_nix_register_reporters(struct rvu_devlink *rvu_dl) rvu_reporters->nix_event_ctx = nix_event_context; rvu_reporters->rvu_hw_nix_intr_reporter = -devlink_health_reporter_create (rvu_dl->dl, &rvu_hw_nix_intr_reporter_ops,0 , rvu); +devlink_health_reporter_create (rvu_dl->dl, + &rvu_hw_nix_intr_reporter_ops, + rvu);if (IS_ERR (rvu_reporters->rvu_hw_nix_intr_reporter)) {dev_warn (rvu->dev,"Failed to create hw_nix_intr reporter, err=%ld\n" ,PTR_ERR (rvu_reporters->rvu_hw_nix_intr_reporter));
@@ -513,7 +515,9 @@ static int rvu_nix_register_reporters(struct rvu_devlink *rvu_dl) } rvu_reporters->rvu_hw_nix_gen_reporter = -devlink_health_reporter_create (rvu_dl->dl, &rvu_hw_nix_gen_reporter_ops,0 , rvu); +devlink_health_reporter_create (rvu_dl->dl, + &rvu_hw_nix_gen_reporter_ops, + rvu);if (IS_ERR (rvu_reporters->rvu_hw_nix_gen_reporter)) {dev_warn (rvu->dev,"Failed to create hw_nix_gen reporter, err=%ld\n" ,PTR_ERR (rvu_reporters->rvu_hw_nix_gen_reporter));
@@ -521,7 +525,9 @@ static int rvu_nix_register_reporters(struct rvu_devlink *rvu_dl) } rvu_reporters->rvu_hw_nix_err_reporter = -devlink_health_reporter_create (rvu_dl->dl, &rvu_hw_nix_err_reporter_ops,0 , rvu); +devlink_health_reporter_create (rvu_dl->dl, + &rvu_hw_nix_err_reporter_ops, + rvu);if (IS_ERR (rvu_reporters->rvu_hw_nix_err_reporter)) {dev_warn (rvu->dev,"Failed to create hw_nix_err reporter, err=%ld\n" ,PTR_ERR (rvu_reporters->rvu_hw_nix_err_reporter));
@@ -529,7 +535,9 @@ static int rvu_nix_register_reporters(struct rvu_devlink *rvu_dl) } rvu_reporters->rvu_hw_nix_ras_reporter = -devlink_health_reporter_create (rvu_dl->dl, &rvu_hw_nix_ras_reporter_ops,0 , rvu); +devlink_health_reporter_create (rvu_dl->dl, + &rvu_hw_nix_ras_reporter_ops, + rvu);if (IS_ERR (rvu_reporters->rvu_hw_nix_ras_reporter)) {dev_warn (rvu->dev,"Failed to create hw_nix_ras reporter, err=%ld\n" ,PTR_ERR (rvu_reporters->rvu_hw_nix_ras_reporter));
@@ -1051,7 +1059,9 @@ static int rvu_npa_register_reporters(struct rvu_devlink *rvu_dl) rvu_reporters->npa_event_ctx = npa_event_context; rvu_reporters->rvu_hw_npa_intr_reporter = -devlink_health_reporter_create (rvu_dl->dl, &rvu_hw_npa_intr_reporter_ops,0 , rvu); +devlink_health_reporter_create (rvu_dl->dl, + &rvu_hw_npa_intr_reporter_ops, + rvu);if (IS_ERR (rvu_reporters->rvu_hw_npa_intr_reporter)) {dev_warn (rvu->dev,"Failed to create hw_npa_intr reporter, err=%ld\n" ,PTR_ERR (rvu_reporters->rvu_hw_npa_intr_reporter));
@@ -1059,7 +1069,9 @@ static int rvu_npa_register_reporters(struct rvu_devlink *rvu_dl) } rvu_reporters->rvu_hw_npa_gen_reporter = -devlink_health_reporter_create (rvu_dl->dl, &rvu_hw_npa_gen_reporter_ops,0 , rvu); +devlink_health_reporter_create (rvu_dl->dl, + &rvu_hw_npa_gen_reporter_ops, + rvu);if (IS_ERR (rvu_reporters->rvu_hw_npa_gen_reporter)) {dev_warn (rvu->dev,"Failed to create hw_npa_gen reporter, err=%ld\n" ,PTR_ERR (rvu_reporters->rvu_hw_npa_gen_reporter));
@@ -1067,7 +1079,9 @@ static int rvu_npa_register_reporters(struct rvu_devlink *rvu_dl) } rvu_reporters->rvu_hw_npa_err_reporter = -devlink_health_reporter_create (rvu_dl->dl, &rvu_hw_npa_err_reporter_ops,0 , rvu); +devlink_health_reporter_create (rvu_dl->dl, + &rvu_hw_npa_err_reporter_ops, + rvu);if (IS_ERR (rvu_reporters->rvu_hw_npa_err_reporter)) {dev_warn (rvu->dev,"Failed to create hw_npa_err reporter, err=%ld\n" ,PTR_ERR (rvu_reporters->rvu_hw_npa_err_reporter));
@@ -1075,7 +1089,9 @@ static int rvu_npa_register_reporters(struct rvu_devlink *rvu_dl) } rvu_reporters->rvu_hw_npa_ras_reporter = -devlink_health_reporter_create (rvu_dl->dl, &rvu_hw_npa_ras_reporter_ops,0 , rvu); +devlink_health_reporter_create (rvu_dl->dl, + &rvu_hw_npa_ras_reporter_ops, + rvu);if (IS_ERR (rvu_reporters->rvu_hw_npa_ras_reporter)) {dev_warn (rvu->dev,"Failed to create hw_npa_ras reporter, err=%ld\n" ,PTR_ERR (rvu_reporters->rvu_hw_npa_ras_reporter));
drivers/net/ethernet/mellanox/mlx5/core/diag/reporter_vnic.c +1 -1
@@ -133,7 +133,7 @@ void mlx5_reporter_vnic_create(struct mlx5_core_dev *dev) health->vnic_reporter =devlink_health_reporter_create (devlink, &mlx5_reporter_vnic_ops, -0 , dev); + dev);if (IS_ERR (health->vnic_reporter)) mlx5_core_warn(dev, "Failed to create vnic reporter, err = %ld\n",
drivers/net/ethernet/mellanox/mlx5/core/en/reporter_rx.c +6 -4
@@ -651,22 +651,24 @@ void mlx5e_reporter_icosq_resume_recovery(struct mlx5e_channel *c)mutex_unlock (&c->icosq_recovery_lock); } +#define MLX5E_REPORTER_RX_GRACEFUL_PERIOD 500 +static const struct devlink_health_reporter_ops mlx5_rx_reporter_ops = { .name ="rx" , .recover = mlx5e_rx_reporter_recover, .diagnose = mlx5e_rx_reporter_diagnose, .dump = mlx5e_rx_reporter_dump, + .default_graceful_period =MLX5E_REPORTER_RX_GRACEFUL_PERIOD , }; -#define MLX5E_REPORTER_RX_GRACEFUL_PERIOD 500 -void mlx5e_reporter_rx_create (struct mlx5e_priv *priv) { +struct devlink_port *port = priv->netdev->devlink_port;struct devlink_health_reporter *reporter; - reporter =devlink_port_health_reporter_create (priv->netdev->devlink_port, + reporter =devlink_port_health_reporter_create (port, &mlx5_rx_reporter_ops, -MLX5E_REPORTER_RX_GRACEFUL_PERIOD , priv); + priv);if (IS_ERR (reporter)) {netdev_warn (priv->netdev,"Failed to create rx reporter, err = %ld\n" ,PTR_ERR (reporter));
drivers/net/ethernet/mellanox/mlx5/core/en/reporter_tx.c +6 -4
@@ -539,22 +539,24 @@ void mlx5e_reporter_tx_ptpsq_unhealthy(struct mlx5e_ptpsq *ptpsq)mlx5e_health_report (priv, priv->tx_reporter, err_str, &err_ctx); } +#define MLX5_REPORTER_TX_GRACEFUL_PERIOD 500 +static const struct devlink_health_reporter_ops mlx5_tx_reporter_ops = { .name ="tx" , .recover = mlx5e_tx_reporter_recover, .diagnose = mlx5e_tx_reporter_diagnose, .dump = mlx5e_tx_reporter_dump, + .default_graceful_period =MLX5_REPORTER_TX_GRACEFUL_PERIOD , }; -#define MLX5_REPORTER_TX_GRACEFUL_PERIOD 500 -void mlx5e_reporter_tx_create (struct mlx5e_priv *priv) { +struct devlink_port *port = priv->netdev->devlink_port;struct devlink_health_reporter *reporter; - reporter =devlink_port_health_reporter_create (priv->netdev->devlink_port, + reporter =devlink_port_health_reporter_create (port, &mlx5_tx_reporter_ops, -MLX5_REPORTER_TX_GRACEFUL_PERIOD , priv); + priv);if (IS_ERR (reporter)) { netdev_warn(priv->netdev, "Failed to create tx reporter, err = %ld\n",
drivers/net/ethernet/mellanox/mlx5/core/en_rep.c +1 -1
@@ -1447,7 +1447,7 @@ static void mlx5e_rep_vnic_reporter_create(struct mlx5e_priv *priv, reporter =devl_port_health_reporter_create (dl_port, &mlx5_rep_vnic_reporter_ops, -0 , rpriv); + rpriv);if (IS_ERR (reporter)) { mlx5_core_err(priv->mdev, "Failed to create representor vnic reporter, err = %ld\n",
drivers/net/ethernet/mellanox/mlx5/core/health.c +24 -17
78 lines not on this page · raw message
drivers/net/ethernet/mellanox/mlxsw/core.c +1 -1
@@ -2043,7 +2043,7 @@ static int mlxsw_core_health_init(struct mlxsw_core *mlxsw_core)return 0 ; fw_fatal =devl_health_reporter_create (devlink, &mlxsw_core_health_fw_fatal_ops, -0 , mlxsw_core); + mlxsw_core);if (IS_ERR (fw_fatal)) {dev_err (mlxsw_core->bus_info->dev,"Failed to create fw fatal reporter" );return PTR_ERR (fw_fatal);
drivers/net/ethernet/qlogic/qed/qed_devlink.c +6 -4
@@ -87,20 +87,22 @@ qed_fw_fatal_reporter_recover(struct devlink_health_reporter *reporter,return 0 ; } +#define QED_REPORTER_FW_GRACEFUL_PERIOD 0 +static const struct devlink_health_reporter_ops qed_fw_fatal_reporter_ops = { .name ="fw_fatal" , .recover = qed_fw_fatal_reporter_recover, .dump = qed_fw_fatal_reporter_dump, + .default_graceful_period =QED_REPORTER_FW_GRACEFUL_PERIOD , }; -#define QED_REPORTER_FW_GRACEFUL_PERIOD 0 -void qed_fw_reporters_create (struct devlink *devlink) {struct qed_devlink *dl =devlink_priv (devlink); - dl->fw_reporter =devlink_health_reporter_create (devlink, &qed_fw_fatal_reporter_ops, -QED_REPORTER_FW_GRACEFUL_PERIOD , dl); + dl->fw_reporter = +devlink_health_reporter_create (devlink, + &qed_fw_fatal_reporter_ops, dl);if (IS_ERR (dl->fw_reporter)) {DP_NOTICE (dl->cdev,"Failed to create fw reporter, err = %ld\n" ,PTR_ERR (dl->fw_reporter));
drivers/net/netdevsim/health.c +2 -2
@@ -183,14 +183,14 @@ int nsim_dev_health_init(struct nsim_dev *nsim_dev, struct devlink *devlink) health->empty_reporter =devl_health_reporter_create (devlink, &nsim_dev_empty_reporter_ops, -0 , health); + health);if (IS_ERR (health->empty_reporter))return PTR_ERR (health->empty_reporter); health->dummy_reporter =devl_health_reporter_create (devlink, &nsim_dev_dummy_reporter_ops, -0 , health); + health);if (IS_ERR (health->dummy_reporter)) { err =PTR_ERR (health->dummy_reporter); goto err_empty_reporter_destroy;
include/net/devlink.h +7 -4
@@ -742,6 +742,8 @@ enum devlink_health_reporter_state {* if priv_ctx is NULL, run a full dump * @diagnose: callback to diagnose the current status * @test: callback to trigger a test event +* @default_graceful_period: default min time (in msec) +between recovery attempts */ struct devlink_health_reporter_ops {
@@ -756,6 +758,7 @@ struct devlink_health_reporter_ops { struct netlink_ext_ack *extack);int (*test)(struct devlink_health_reporter *reporter,struct netlink_ext_ack *extack); +u64 default_graceful_period; };/**
@@ -1924,22 +1927,22 @@ void devlink_fmsg_binary_pair_put(struct devlink_fmsg *fmsg, const char *name,struct devlink_health_reporter *devl_port_health_reporter_create (struct devlink_port *port,const struct devlink_health_reporter_ops *ops, -u64 graceful_period,void *priv); +void *priv);struct devlink_health_reporter *devlink_port_health_reporter_create (struct devlink_port *port,const struct devlink_health_reporter_ops *ops, -u64 graceful_period,void *priv); +void *priv);struct devlink_health_reporter *devl_health_reporter_create (struct devlink *devlink,const struct devlink_health_reporter_ops *ops, -u64 graceful_period,void *priv); +void *priv);struct devlink_health_reporter *devlink_health_reporter_create (struct devlink *devlink,const struct devlink_health_reporter_ops *ops, -u64 graceful_period,void *priv); +void *priv);void devl_health_reporter_destroy (struct devlink_health_reporter *reporter);
net/devlink/health.c +11 -17
@@ -108,11 +108,11 @@ devlink_port_health_reporter_find_by_name(struct devlink_port *devlink_port,static struct devlink_health_reporter *__devlink_health_reporter_create (struct devlink *devlink,const struct devlink_health_reporter_ops *ops, -u64 graceful_period,void *priv) +void *priv) {struct devlink_health_reporter *reporter; -if (WARN_ON (graceful_period && !ops->recover)) +if (WARN_ON (ops->default_graceful_period && !ops->recover))return ERR_PTR (-EINVAL ); reporter =kzalloc (sizeof (*reporter),GFP_KERNEL );
@@ -122,7 +122,7 @@ __devlink_health_reporter_create(struct devlink *devlink, reporter->priv = priv; reporter->ops = ops; reporter->devlink = devlink; - reporter->graceful_period = graceful_period; + reporter->graceful_period = ops->default_graceful_period; reporter->auto_recover = !!ops->recover; reporter->auto_dump = !!ops->dump;return reporter;
@@ -134,13 +134,12 @@ __devlink_health_reporter_create(struct devlink *devlink,* * @port: devlink_port to which health reports will relate * @ops: devlink health reporter ops -* @graceful_period: min time (in msec) between recovery attempts * @priv: driver priv pointer */ struct devlink_health_reporter *devl_port_health_reporter_create (struct devlink_port *port,const struct devlink_health_reporter_ops *ops, -u64 graceful_period,void *priv) +void *priv) {struct devlink_health_reporter *reporter;
@@ -150,8 +149,7 @@ devl_port_health_reporter_create(struct devlink_port *port, ops->name))return ERR_PTR (-EEXIST ); - reporter =__devlink_health_reporter_create (port->devlink, ops, - graceful_period, priv); + reporter =__devlink_health_reporter_create (port->devlink, ops, priv);if (IS_ERR (reporter))return reporter;
@@ -164,14 +162,13 @@ EXPORT_SYMBOL_GPL(devl_port_health_reporter_create);struct devlink_health_reporter *devlink_port_health_reporter_create (struct devlink_port *port,const struct devlink_health_reporter_ops *ops, -u64 graceful_period,void *priv) +void *priv) {struct devlink_health_reporter *reporter;struct devlink *devlink = port->devlink;devl_lock (devlink); - reporter =devl_port_health_reporter_create (port, ops, - graceful_period, priv); + reporter =devl_port_health_reporter_create (port, ops, priv);devl_unlock (devlink);return reporter; }
@@ -182,13 +179,12 @@ EXPORT_SYMBOL_GPL(devlink_port_health_reporter_create);* * @devlink: devlink instance which the health reports will relate * @ops: devlink health reporter ops -* @graceful_period: min time (in msec) between recovery attempts * @priv: driver priv pointer */ struct devlink_health_reporter *devl_health_reporter_create (struct devlink *devlink,const struct devlink_health_reporter_ops *ops, -u64 graceful_period,void *priv) +void *priv) {struct devlink_health_reporter *reporter;
@@ -197,8 +193,7 @@ devl_health_reporter_create(struct devlink *devlink,if (devlink_health_reporter_find_by_name (devlink, ops->name))return ERR_PTR (-EEXIST ); - reporter =__devlink_health_reporter_create (devlink, ops, - graceful_period, priv); + reporter =__devlink_health_reporter_create (devlink, ops, priv);if (IS_ERR (reporter))return reporter;
@@ -210,13 +205,12 @@ EXPORT_SYMBOL_GPL(devl_health_reporter_create);struct devlink_health_reporter *devlink_health_reporter_create (struct devlink *devlink,const struct devlink_health_reporter_ops *ops, -u64 graceful_period,void *priv) +void *priv) {struct devlink_health_reporter *reporter;devl_lock (devlink); - reporter =devl_health_reporter_create (devlink, ops, - graceful_period, priv); + reporter =devl_health_reporter_create (devlink, ops, priv);devl_unlock (devlink);return reporter; }
Signature · 1 line
2.31.1
Tariq Toukan
maintainerPATCH v3 2/5 devlink: Move health reporter recovery abort logic to a separate function
In reply to Tariq ToukanFrom: Shahar Shitrit <[email protected]>
Extract the health reporter recovery abort logic into a separate function devlink_health_recover_abort().
The function encapsulates the conditions for aborting recovery:
- When auto-recovery is disabled
- When previous error wasn't recovered
- When within the grace period after last recovery
--- net/devlink/health.c | 31 +++++++++++++++++++++++-------- 1 file changed, 23 insertions(+), 8 deletions(-)
net/devlink/health.c +23 -8
@@ -586,12 +586,33 @@ static int devlink_health_do_dump(struct devlink_health_reporter *reporter,return err; } +static bool +devlink_health_recover_abort (struct devlink_health_reporter *reporter, +enum devlink_health_reporter_state prev_state) +{ +unsigned long recover_ts_threshold; + +if (!reporter->auto_recover) +return false; + +/* abort if the previous error wasn't recovered */ +if (prev_state !=DEVLINK_HEALTH_REPORTER_STATE_HEALTHY ) +return true; + + recover_ts_threshold = reporter->last_recovery_ts + +msecs_to_jiffies (reporter->graceful_period); +if (reporter->last_recovery_ts && reporter->recovery_count && +time_is_after_jiffies (recover_ts_threshold)) +return true; + +return false; +} +int devlink_health_report (struct devlink_health_reporter *reporter,const char *msg,void *priv_ctx) {enum devlink_health_reporter_state prev_health_state;struct devlink *devlink = reporter->devlink; -unsigned long recover_ts_threshold;int ret;/* write a log message of the current error */
@@ -602,13 +623,7 @@ int devlink_health_report(struct devlink_health_reporter *reporter, reporter->health_state =DEVLINK_HEALTH_REPORTER_STATE_ERROR ;devlink_recover_notify (reporter,DEVLINK_CMD_HEALTH_REPORTER_RECOVER ); -/* abort if the previous error wasn't recovered */ - recover_ts_threshold = reporter->last_recovery_ts + -msecs_to_jiffies (reporter->graceful_period); -if (reporter->auto_recover && - (prev_health_state !=DEVLINK_HEALTH_REPORTER_STATE_HEALTHY || - (reporter->last_recovery_ts && reporter->recovery_count && -time_is_after_jiffies (recover_ts_threshold)))) { +if (devlink_health_recover_abort (reporter, prev_health_state)) { trace_devlink_health_recover_aborted(devlink, reporter->ops->name, reporter->health_state,
Signature · 1 line
2.31.1
Tariq Toukan
maintainerPATCH v3 3/5 devlink: Introduce error burst period for health reporter
In reply to Tariq ToukanFrom: Shahar Shitrit <[email protected]>
Currently, the devlink health reporter starts the grace period immediately after handling an error, blocking any further recoveries until it finished.
However, when a single root cause triggers multiple errors in a short time frame, it is desirable to treat them as a bulk of errors and to allow their recoveries, avoiding premature blocking of subsequent related errors, and reducing the risk of inconsistent or incomplete error handling.
To address this, introduce a configurable error burst period for devlink health reporter. Start this period when the first error is handled, and allow recovery attempts for reported errors during this window. Once error burst period expires, begin the grace period to block further recoveries until it concludes.
Timeline summary:
----|--------|------------------------------/----------------------/--
error is error is error burst period grace period
reported recovered (recoveries allowed) (recoveries blocked)
For calculating the error burst period duration, use the same last_recovery_ts as the grace period. Update it on recovery only when the error burst period is inactive (either disabled or at the first error).
This patch implements the framework for the error burst period and effectively sets its value to 0 at reporter creation, so the current behavior remains unchanged, which ensures backward compatibility.
A downstream patch will make the error burst period configurable.
--- include/net/devlink.h | 4 ++++ net/devlink/health.c | 22 +++++++++++++++++++++- 2 files changed, 25 insertions(+), 1 deletion(-)
include/net/devlink.h +4 -0
@@ -744,6 +744,9 @@ enum devlink_health_reporter_state {* @test: callback to trigger a test event * @default_graceful_period: default min time (in msec) between recovery attempts +* @default_error_burst_period: default time (in msec) for +* error recoveries before +* starting the grace period */ struct devlink_health_reporter_ops {
@@ -759,6 +762,7 @@ struct devlink_health_reporter_ops {int (*test)(struct devlink_health_reporter *reporter,struct netlink_ext_ack *extack);u64 default_graceful_period; +u64 default_error_burst_period; };/**
net/devlink/health.c +21 -1
@@ -60,6 +60,7 @@ struct devlink_health_reporter {struct devlink_port *devlink_port;struct devlink_fmsg *dump_fmsg;u64 graceful_period; +u64 error_burst_period;bool auto_recover;bool auto_dump;u8 health_state;
@@ -123,6 +124,7 @@ __devlink_health_reporter_create(struct devlink *devlink, reporter->ops = ops; reporter->devlink = devlink; reporter->graceful_period = ops->default_graceful_period; + reporter->error_burst_period = ops->default_error_burst_period; reporter->auto_recover = !!ops->recover; reporter->auto_dump = !!ops->dump;return reporter;
@@ -508,11 +510,25 @@ static void devlink_recover_notify(struct devlink_health_reporter *reporter,devlink_nl_notify_send_desc (devlink, msg, &desc); } +static bool +devlink_health_reporter_burst_period_active (struct devlink_health_reporter *reporter) +{ +unsigned long burst_threshold = reporter->last_recovery_ts + +msecs_to_jiffies (reporter->error_burst_period); + +return time_is_after_jiffies (burst_threshold); +} +void devlink_health_reporter_recovery_done (struct devlink_health_reporter *reporter) { reporter->recovery_count++; - reporter->last_recovery_ts = jiffies; +if (!devlink_health_reporter_burst_period_active (reporter)) +/* When error burst period is set, last_recovery_ts marks the +* first recovery within the burst period, not necessarily the +* last one. +*/ + reporter->last_recovery_ts = jiffies; }EXPORT_SYMBOL_GPL (devlink_health_reporter_recovery_done);
@@ -599,7 +615,11 @@ devlink_health_recover_abort(struct devlink_health_reporter *reporter,if (prev_state !=DEVLINK_HEALTH_REPORTER_STATE_HEALTHY )return true; +if (devlink_health_reporter_burst_period_active (reporter)) +return false; + recover_ts_threshold = reporter->last_recovery_ts + +msecs_to_jiffies (reporter->error_burst_period) +msecs_to_jiffies (reporter->graceful_period);if (reporter->last_recovery_ts && reporter->recovery_count &&time_is_after_jiffies (recover_ts_threshold))
Signature · 1 line
2.31.1
Tariq Toukan
maintainerPATCH v3 4/5 devlink: Make health reporter error burst period configurable
In reply to Tariq ToukanFrom: Shahar Shitrit <[email protected]>
Enable configuration of the error burst period — a time window starting from the first error recovery, during which the reporter allows recovery attempts for each reported error.
This feature is helpful when a single underlying issue causes multiple errors, as it delays the start of the grace period to allow sufficient time for recovering all related errors. For example, if multiple TX queues time out simultaneously, a sufficient error burst period could allow all affected TX queues to be recovered within that window. Without this period, only the first TX queue that reports a timeout will undergo recovery, while the remaining TX queues will be blocked once the grace period begins.
Configuration example:
$ devlink health set pci/0000:00:09.0 reporter tx error_burst_period 500
Configuration example with ynl:./tools/net/ynl/pyynl/cli.py \
--spec Documentation/netlink/specs/devlink.yaml \
--do health-reporter-set --json '{
"bus-name": "auxiliary",
"dev-name": "mlx5_core.eth.0", "port-index": 65535, "health-reporter-name": "tx", "health-reporter-error-burst-period": 500
}'
--- Documentation/netlink/specs/devlink.yaml | 6 ++++ .../networking/devlink/devlink-health.rst | 2 +- include/uapi/linux/devlink.h | 2 ++ net/devlink/health.c | 30 +++++++++++++++++-- net/devlink/netlink_gen.c | 5 ++-- 5 files changed, 39 insertions(+), 6 deletions(-)
Documentation/netlink/specs/devlink.yaml +6 -0
@@ -853,6 +853,9 @@ attribute-sets: type: nest multi-attr: true nested-attributes: dl-rate-tc-bws + - + name: health-reporter-error-burst-period + type: u64 - name: dl-dev-stats subset-of: devlink
@@ -1216,6 +1219,8 @@ attribute-sets: name: health-reporter-dump-ts-ns - name: health-reporter-auto-dump + - + name: health-reporter-error-burst-period - name: dl-attr-stats
@@ -1961,6 +1966,7 @@ operations: - health-reporter-graceful-period - health-reporter-auto-recover - health-reporter-auto-dump + - health-reporter-error-burst-period - name: health-reporter-recover
Documentation/networking/devlink/devlink-health.rst +1 -1
@@ -50,7 +50,7 @@ Once an error is reported, devlink health will perform the following actions: * Auto recovery attempt is being done. Depends on: - Auto-recovery configuration - - Grace period vs. time passed since last recover + - Grace period (and error burst period) vs. time passed since last recover Devlink formatted message =========================
include/uapi/linux/devlink.h +2 -0
@@ -636,6 +636,8 @@ enum devlink_attr {DEVLINK_ATTR_RATE_TC_BWS ,/* nested */ + DEVLINK_ATTR_HEALTH_REPORTER_ERR_BURST_PERIOD, /* u64 */ +/* Add new attributes above here, update the spec in * Documentation/netlink/specs/devlink.yaml and re-generate * net/devlink/netlink_gen.c.
net/devlink/health.c +27 -3
@@ -113,7 +113,9 @@ __devlink_health_reporter_create(struct devlink *devlink, {struct devlink_health_reporter *reporter; -if (WARN_ON (ops->default_graceful_period && !ops->recover)) +if (WARN_ON (ops->default_error_burst_period && + !ops->default_graceful_period) || +WARN_ON (ops->default_graceful_period && !ops->recover))return ERR_PTR (-EINVAL ); reporter =kzalloc (sizeof (*reporter),GFP_KERNEL );
@@ -293,6 +295,11 @@ devlink_nl_health_reporter_fill(struct sk_buff *msg, devlink_nl_put_u64(msg, DEVLINK_ATTR_HEALTH_REPORTER_GRACEFUL_PERIOD, reporter->graceful_period)) goto reporter_nest_cancel; +if (reporter->ops->recover && +devlink_nl_put_u64 (msg, +DEVLINK_ATTR_HEALTH_REPORTER_ERR_BURST_PERIOD , + reporter->error_burst_period)) + goto reporter_nest_cancel;if (reporter->ops->recover &&nla_put_u8 (msg,DEVLINK_ATTR_HEALTH_REPORTER_AUTO_RECOVER , reporter->auto_recover))
@@ -458,16 +465,33 @@ int devlink_nl_health_reporter_set_doit(struct sk_buff *skb,if (!reporter->ops->recover && (info->attrs[DEVLINK_ATTR_HEALTH_REPORTER_GRACEFUL_PERIOD ] || - info->attrs[DEVLINK_ATTR_HEALTH_REPORTER_AUTO_RECOVER ])) + info->attrs[DEVLINK_ATTR_HEALTH_REPORTER_AUTO_RECOVER ] || + info->attrs[DEVLINK_ATTR_HEALTH_REPORTER_ERR_BURST_PERIOD ]))return -EOPNOTSUPP ;if (!reporter->ops->dump && info->attrs[DEVLINK_ATTR_HEALTH_REPORTER_AUTO_DUMP ])return -EOPNOTSUPP ; -if (info->attrs[DEVLINK_ATTR_HEALTH_REPORTER_GRACEFUL_PERIOD ]) +if (info->attrs[DEVLINK_ATTR_HEALTH_REPORTER_GRACEFUL_PERIOD ]) { reporter->graceful_period =nla_get_u64 (info->attrs[DEVLINK_ATTR_HEALTH_REPORTER_GRACEFUL_PERIOD ]); +if (!reporter->graceful_period) + reporter->error_burst_period =0 ; + } + +if (info->attrs[DEVLINK_ATTR_HEALTH_REPORTER_ERR_BURST_PERIOD ]) { +u64 burst_period = +nla_get_u64 (info->attrs[DEVLINK_ATTR_HEALTH_REPORTER_ERR_BURST_PERIOD ]); + +if (!reporter->graceful_period && burst_period) { +NL_SET_ERR_MSG_MOD (info->extack, +"Cannot set error burst period without a grace period." ); +return -EINVAL ; + } + + reporter->error_burst_period = burst_period; + }if (info->attrs[DEVLINK_ATTR_HEALTH_REPORTER_AUTO_RECOVER ]) reporter->auto_recover =
net/devlink/netlink_gen.c +3 -2
@@ -389,7 +389,7 @@ static const struct nla_policy devlink_health_reporter_get_dump_nl_policy[DEVLIN };/* DEVLINK_CMD_HEALTH_REPORTER_SET - do */ -static const struct nla_policy devlink_health_reporter_set_nl_policy[DEVLINK_ATTR_HEALTH_REPORTER_AUTO_DUMP +1 ] = { +static const struct nla_policy devlink_health_reporter_set_nl_policy[DEVLINK_ATTR_HEALTH_REPORTER_ERR_BURST_PERIOD +1 ] = { [DEVLINK_ATTR_BUS_NAME ] = { .type =NLA_NUL_STRING , }, [DEVLINK_ATTR_DEV_NAME ] = { .type =NLA_NUL_STRING , }, [DEVLINK_ATTR_PORT_INDEX ] = { .type =NLA_U32 , },
@@ -397,6 +397,7 @@ static const struct nla_policy devlink_health_reporter_set_nl_policy[DEVLINK_ATT [DEVLINK_ATTR_HEALTH_REPORTER_GRACEFUL_PERIOD] = { .type = NLA_U64, }, [DEVLINK_ATTR_HEALTH_REPORTER_AUTO_RECOVER] = { .type = NLA_U8, }, [DEVLINK_ATTR_HEALTH_REPORTER_AUTO_DUMP] = { .type = NLA_U8, }, + [DEVLINK_ATTR_HEALTH_REPORTER_ERR_BURST_PERIOD] = { .type = NLA_U64, }, };/* DEVLINK_CMD_HEALTH_REPORTER_RECOVER - do */
@@ -1032,7 +1033,7 @@ const struct genl_split_ops devlink_nl_ops[74] = { .doit = devlink_nl_health_reporter_set_doit, .post_doit = devlink_nl_post_doit, .policy = devlink_health_reporter_set_nl_policy, - .maxattr = DEVLINK_ATTR_HEALTH_REPORTER_AUTO_DUMP, + .maxattr = DEVLINK_ATTR_HEALTH_REPORTER_ERR_BURST_PERIOD, .flags = GENL_ADMIN_PERM | GENL_CMD_CAP_DO, }, {
Signature · 1 line
2.31.1
Tariq Toukan
maintainerPATCH v3 5/5 net/mlx5e: Set default error burst period for TX and RX reporters
In reply to Tariq ToukanFrom: Shahar Shitrit <[email protected]>
System errors can sometimes cause multiple errors to be reported to the TX reporter at the same time. For instance, lost interrupts may cause several SQs to time out simultaneously. When dev_watchdog notifies the driver for that, it iterates over all SQs to trigger recovery for the timed-out ones, via TX health reporter. However, grace period allows only one recovery at a time, so only the first SQ recovers while others remain blocked. Since no further recoveries are allowed during the grace period, subsequent errors cause the reporter to enter an ERROR state, requiring manual intervention.
To address this, set the TX reporter's default error burst period to 0.5 second. This allows the reporter to detect and handle all timed-out SQs within this window before initiating the grace period.
To account for the possibility of a similar issue in the RX reporter, its default error burst period is also configured.
Additionally, while here, align the TX definition prefix with the RX, as these are used only in EN driver.
--- drivers/net/ethernet/mellanox/mlx5/core/en/reporter_rx.c | 2 ++ drivers/net/ethernet/mellanox/mlx5/core/en/reporter_tx.c | 7 +++++-- 2 files changed, 7 insertions(+), 2 deletions(-)
drivers/net/ethernet/mellanox/mlx5/core/en/reporter_rx.c +2 -0
@@ -652,6 +652,7 @@ void mlx5e_reporter_icosq_resume_recovery(struct mlx5e_channel *c) }#define MLX5E_REPORTER_RX_GRACEFUL_PERIOD 500 +#define MLX5E_REPORTER_RX_ERROR_BURST_PERIOD 500static const struct devlink_health_reporter_ops mlx5_rx_reporter_ops = { .name ="rx" ,
@@ -659,6 +660,7 @@ static const struct devlink_health_reporter_ops mlx5_rx_reporter_ops = { .diagnose = mlx5e_rx_reporter_diagnose, .dump = mlx5e_rx_reporter_dump, .default_graceful_period = MLX5E_REPORTER_RX_GRACEFUL_PERIOD, + .default_error_burst_period = MLX5E_REPORTER_RX_ERROR_BURST_PERIOD, };void mlx5e_reporter_rx_create (struct mlx5e_priv *priv)
drivers/net/ethernet/mellanox/mlx5/core/en/reporter_tx.c +5 -2
@@ -539,14 +539,17 @@ void mlx5e_reporter_tx_ptpsq_unhealthy(struct mlx5e_ptpsq *ptpsq)mlx5e_health_report (priv, priv->tx_reporter, err_str, &err_ctx); } -#define MLX5_REPORTER_TX_GRACEFUL_PERIOD 500 +#define MLX5E_REPORTER_TX_GRACEFUL_PERIOD 500 +#define MLX5E_REPORTER_TX_ERROR_BURST_PERIOD 500static const struct devlink_health_reporter_ops mlx5_tx_reporter_ops = { .name ="tx" , .recover = mlx5e_tx_reporter_recover, .diagnose = mlx5e_tx_reporter_diagnose, .dump = mlx5e_tx_reporter_dump, - .default_graceful_period =MLX5_REPORTER_TX_GRACEFUL_PERIOD , + .default_graceful_period =MLX5E_REPORTER_TX_GRACEFUL_PERIOD , + .default_error_burst_period = +MLX5E_REPORTER_TX_ERROR_BURST_PERIOD , };void mlx5e_reporter_tx_create (struct mlx5e_priv *priv)
Signature · 1 line
2.31.1
Jakub Kicinski
maintainerRe: [PATCH net-next V3 1/5] devlink: Move graceful period parameter to reporter ops
In reply to Tariq Toukaninclude/net/devlink.h enum devlink_health_reporter_state { · line 747
Quoted 4 lines · On Wed, 13 Aug 2025 21:55:45 +0300 Tariq Toukan wrote:
* @test: callback to trigger a test event
+ * @default_graceful_period: default min time (in msec)include/net/devlink.h +1
-0+between recovery attempts */
Missing * at the start of the line.
Jakub Kicinski
maintainerRe: [PATCH net-next V3 3/5] devlink: Introduce error burst period for health reporter
In reply to Tariq ToukanQuoted 3 lines · On Wed, 13 Aug 2025 21:55:47 +0300 Tariq Toukan wrote:
+ * @default_error_burst_period: default time (in msec) for
+ * error recoveries before
+ * starting the grace period
FWIW you don't have to indent the continuation lines this much, one tab is enough to make it clear that it's a continuation.
net/devlink/health.c static void devlink_recover_notify(struct devlink_health_reporter *reporter, · line 514
Quoted 2 lines
net/devlink/health.c +2
-0+static bool +devlink_health_reporter_burst_period_active (struct devlink_health_reporter *reporter)
Not sure what it means for a period to be active.
devlink_health_reporter_in_burst()
Jakub Kicinski
maintainerRe: [PATCH net-next V3 4/5] devlink: Make health reporter error burst period configurable
In reply to Tariq ToukanDocumentation/netlink/specs/devlink.yaml attribute-sets: · line 857
Quoted 10 lines · On Wed, 13 Aug 2025 21:55:48 +0300 Tariq Toukan wrote:
Documentation/netlink/specs/devlink.yaml +2
-0@@ -853,6 +853,9 @@ attribute-sets: type: nest multi-attr: true nested-attributes: dl-rate-tc-bws + - + name: health-reporter-error-burst-period
the "graceful-period" does not have the word "error" in it. Why is it necessary to include it in this parameter? What else would be bursting in an error reporter if not errors?
Documentation/netlink/specs/devlink.yaml attribute-sets: · line 858
Quoted 1 line
Documentation/netlink/specs/devlink.yaml +1
-0+ type: u64
could you add a doc: here?
Documentation/netlink/specs/devlink.yaml attribute-sets:
Quoted 5 lines
Documentation/netlink/specs/devlink.yaml +1
-0- name: dl-dev-stats subset-of: devlink + DEVLINK_ATTR_HEALTH_REPORTER_ERR_BURST_PERIOD, /* u64 */
The _ERR here won't work if you used _ERROR in YAML. The naming in the YAML spec must match the C naming exactly.
Signature · 1 line
pw-bot: cr
Re: [PATCH net-next V3 4/5] devlink: Make health reporter error burst period configurable
Quoted 15 lines · Jakub Kicinski
Documentation/netlink/specs/devlink.yaml attribute-sets: · line 857
Quoted 10 lines · On Wed, 13 Aug 2025 21:55:48 +0300 Tariq Toukan wrote:
Documentation/netlink/specs/devlink.yaml +2
-0@@ -853,6 +853,9 @@ attribute-sets: type: nest multi-attr: true nested-attributes: dl-rate-tc-bws + - + name: health-reporter-error-burst-periodthe "graceful-period" does not have the word "error" in it. Why is it necessary to include it in this parameter? What else would be bursting in an error reporter if not errors?
I see. Would you suggest renaming it to "burst period" through the entire series?
for example in devlink.h:default_error_burst_period --> default_burst_period
Quoted 13 lines
Documentation/netlink/specs/devlink.yaml attribute-sets: · line 858
Quoted 2 lines
Documentation/netlink/specs/devlink.yaml +1
-0+ type: u64could you add a doc: here?
Documentation/netlink/specs/devlink.yaml attribute-sets:
Quoted 5 lines
Documentation/netlink/specs/devlink.yaml +1
-0- name: dl-dev-stats subset-of: devlink + DEVLINK_ATTR_HEALTH_REPORTER_ERR_BURST_PERIOD, /* u64 */The
_ERRhere won't work if you used_ERRORin YAML. The naming in the YAML spec must match the C naming exactly.
Jakub Kicinski
maintainerRe: [PATCH net-next V3 4/5] devlink: Make health reporter error burst period configurable
Quoted 17 lines · On Sun, 17 Aug 2025 19:08:47 +0300 Shahar Shitrit wrote:
Quoted 15 lines · Jakub Kicinski
Documentation/netlink/specs/devlink.yaml attribute-sets: · line 857
Quoted 10 lines · On Wed, 13 Aug 2025 21:55:48 +0300 Tariq Toukan wrote:
Documentation/netlink/specs/devlink.yaml +2
-0@@ -853,6 +853,9 @@ attribute-sets: type: nest multi-attr: true nested-attributes: dl-rate-tc-bws + - + name: health-reporter-error-burst-periodthe "graceful-period" does not have the word "error" in it. Why is it necessary to include it in this parameter? What else would be bursting in an error reporter if not errors?
Quoted 4 lines
I see. Would you suggest renaming it to "burst period" through the entire series?
for example indevlink.h:default_error_burst_period-->default_burst_period
Yes, AFAICT it won't result in any loss of clarity.