ENUM IWL_MVM_LOW_LATENCY_CAUSE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

enum iwl_mvm_low_latency_cause β€” the whole reason-list for why low latency mode got switched on, bestie πŸ’… (this is from the kernel API manual, enum iwl_mvm...atency_cause(9), and yes the header is literally that)


✨ SYNOPSIS ✨

enum iwl_mvm_low_latency_cause {
    LOW_LATENCY_TRAFFIC ,
    LOW_LATENCY_DEBUGFS ,
    LOW_LATENCY_VCMD ,
    LOW_LATENCY_VIF_TYPE ,
    LOW_LATENCY_DEBUGFS_FORCE_ENABLE ,
    LOW_LATENCY_DEBUGFS_FORCE

};

🌸 DESCRIPTION 🌸

Okay so picture this: low latency mode is on, and the kernel wants receipts on who asked for it. This enum is literally the cause list β€” every reason gets its own little constant. No cap, it's giving "notes app of my feelings" but for wifi latency 🫢


πŸ‘‘ Constants

  • LOW_LATENCY_TRAFFIC β€” bestie this one means low latency traffic was detected, like the network sniffed it out itself πŸ”₯
  • LOW_LATENCY_DEBUGFS β€” low latency mode got set from debugfs (you did it, manually, on purpose πŸ’…)
  • LOW_LATENCY_VCMD β€” low latency mode got set from a vendor command πŸ‘€
  • LOW_LATENCY_VIF_TYPE β€” low latency mode got set because of the vif type (ap), so the interface type forced the whole vibe ⭐
  • LOW_LATENCY_DEBUGFS_FORCE_ENABLE β€” this one just indicates that force mode is enabled, fr fr. The actual set/unset is done with LOW_LATENCY_DEBUGFS_FORCE β€” do not confuse them, I'm begging πŸ™ˆ
  • LOW_LATENCY_DEBUGFS_FORCE β€” the low latency force mode from debugfs. Set this together with the LOW_LATENCY_DEBUGFS_FORCE_ENABLE flag in low_latency. That's the assignment. πŸŽ€
Miss the flag pairing and you're just gonna be sitting there confused wondering why nothing happened. Lowkey tragic. 😭

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/net/wireless/intel/iwlwifi/mvm/mvm.h, plus the whole friend group:

  • struct iwl_mvm_mod_params(9)
  • enum iwl_power_scheme(9)
  • enum iwl_mvm_low_latency_force(9)
  • struct iwl_mvm_link_bf_data(9)
  • struct iwl_probe_resp_data(9)
  • struct iwl_mvm_vif_link_info(9)
  • struct iwl_mvm_vif(9)
  • struct iwl_mvm_tt_mgmt(9)
  • struct iwl_mvm_thermal_device(9)
  • struct iwl_mvm_reorder_buffer(9)
  • struct iwl_mvm_reorder_buf_entry(9)
  • struct iwl_mvm_baid_data(9)
  • struct iwl_mvm_tvqm_txq_info(9)
  • struct iwl_mvm_acs_survey_channel(9)
  • enum iwl_mvm_status(9)
  • struct iwl_mvm_roc_ops(9)
  • struct iwl_mvm_switch_vif_chanctx_ops(9)

okay that's the whole page, you ate it, go touch grass now 🌈

Signed, sealed, delivered: this came from ./drivers/net/wireless/intel/i... and it's dated October 2026, and the manual is enum iwl_mvm...atency_cause(9). Mwah πŸ’–

πŸ“¦ where this page comes from