libnvme(9)

πŸ“¦ version 3.2, in arch rolling

πŸ’… libnvme(9) β€” API Manual πŸ’…

Okay bestie, welcome to the libnvme(9) API Manual β€” this is the page for enum nvme_log_phy_rx_eom_action, which sounds like a whole mouthful but is actually just a tiny lil enum about measuring stuff. You got this. πŸ¦‹


✨ NAME ✨

enum nvme_log_phy_rx_eom_action β€” Physical Interface Receiver Eye Opening Measurement Action

Like, it's literally the enum that tells you what action to take during a Physical Interface Receiver Eye Opening Measurement. Eye opening measurement, yes, that's a real thing, no cap. πŸ‘€


🌸 SYNOPSIS 🌸

enum nvme_log_phy_rx_eom_action {
    NVME_LOG_PHY_RX_EOM_READ ,
    NVME_LOG_PHY_RX_EOM_START_READ ,
    NVME_LOG_PHY_RX_EOM_ABORT_CLEAR

};

That's the whole enum, bestie β€” three constants, comma-separated, with a lil blank line before the closing brace. Copy it exactly, don't be doing your own thing with it. πŸ’…


πŸŽ€ Constants πŸŽ€

Three constants, three vibes. Here they are:

  • NVME_LOG_PHY_RX_EOM_READ β€” Read Log Data. Just read it. That's the whole assignment. πŸ“–
  • NVME_LOG_PHY_RX_EOM_START_READ β€” Start Measurement and Read Log Data. Two things at once, main character energy fr fr. ✨
  • NVME_LOG_PHY_RX_EOM_ABORT_CLEAR β€” Abort Measurement and Clear Log Data. When it's giving nothing, you abort and clear. Iconic. πŸ’€

Lowkey a reminder: these are the only constants in the enum, so don't go inventing extra ones, okay? The manpage says three, so it's three. Periodt. 🫢

And that's the page, bestie β€” you ate that. πŸ’– This was enum nvme_log_phy_rx_eom_action from the libnvme(9) API Manual, dated October 2026. Go forth and measure those eye openings. πŸ§šβ€β™€οΈπŸŒˆβ­

πŸ“¦ where this page comes from