STRUCT PHY_MSE_SNAPSHOT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ struct phy_mse_snapshot(9) β€” Kernel API Manual πŸ¦‹

okay bestie, this page is literally about a struct that holds your Mean Square Error diagnostics snapshot, and it’s lowkey important if you’re poking at PHY stuff πŸ’…

πŸŽ€ NAME πŸŽ€

struct phy_mse_snapshot β€” a snapshot of Mean Square Error (MSE) diagnostics ✨

✨ SYNOPSIS ✨

here’s the whole struct, no edits, no vibes-only summaries:

struct phy_mse_snapshot {
           u64 average_mse;
           u64 peak_mse;
           u64 worst_peak_mse;
        };

πŸ’– Members πŸ’–

  • average_mse β€” the average MSE value over the measurement window. OPEN Alliance references MSE as a DCQ metric; recommends 2^16 symbols and 0..511 scaling. Exact scale and refresh are vendor-specific. (100BASE-T1 TC1 v1.0 6.1.1; 1000BASE-T1 TC12 v2.2 6.1.1).
  • peak_mse β€” the peak MSE value observed within the measurement window. For 100BASE-T1, "pMSE" is optional and may be implemented via a sliding 128-symbol window with periodic capture; not standardized for 1000BASE-T1. (100BASE-T1 TC1 v1.0 6.1.3, Table "DCQ.peakMSE").
  • worst_peak_mse β€” a latched high-water mark of the peak MSE since last read (read-to-clear if implemented). OPEN Alliance shows a latched "worst case peak MSE" for 100BASE-T1 pMSE; availability/semantics outside that are vendor-specific. (100BASE-T1 TC1 v1.0 6.1.3, DCQ.peakMSE high byte; 1000BASE-T1 TC12 v2.2 treats DCQ details as vendor-specific.)

🌈 Description 🌈

Holds a set of MSE diagnostic values that were all captured from a single measurement window. cute and coherent like that 🫢

Values are raw, device-scaled and not normalized. Use struct phy_mse_capability to interpret the scale and sampling window. periodt πŸ’…

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./include/linux/phy.h β€” plus the whole bestie squad right here:


okay that’s the whole page, bestie πŸ’… source/version is ./include/linux, date is October 2026, and the main character is literally struct phy_mse_snapshot(9) 🫢✨

πŸ“¦ where this page comes from