NVME_GET_LOG_CREATE_TELEMETRY_HOST(2)

πŸ’– nvme_get_log_create_telemetry_host(2) πŸ’–

okay bestie, welcome to the libnvme API manual ✨ pull up a chair, we're doing a man page and honestly? it's giving main character energy, sit down 🫢


✨ NAME ✨

nvme_get_log_create_telemetry_host β€” Create host telemetry log 🌸

Like, it literally does what it says on the tin. It makes the host telemetry log. No cap. πŸ’…


✨ SYNOPSIS ✨

int nvme_get_log_create_telemetry_host (int fd , struct nvme_telemetry_log *log );

look at her. so demure. so mindful. two args and a dream πŸ’œ


✨ ARGUMENTS ✨

  • fd β€” File descriptor of nvme device πŸ”₯ this is the whole vibe check β€” you handed over an fd, it's the nvme device's official little handle, and the function is gonna use it to talk to the drive.
  • log β€” Userspace address of the log payload ✨ this is where the log payload lives in your userspace, bestie. you point, it fills. that's the deal 🀝

✨ RETURN ✨

so here's the tea β˜• this function is gonna hand you back:

  • The nvme command status β€” if a response was received πŸŽ€ (go peek at enum nvme_status_field for the whole menu of what those statuses mean, iykyk)
  • -1 β€” with errno set, otherwise 😭
heads up bestie: that "otherwise" is doing a LOT of heavy lifting. if you get a response, you get a status. if you don't? -1 and errno is telling you the whole story. check it, fr fr. don't just stare at the -1 like it owes you money πŸ’€

and that's the whole page, periodt πŸ‘‘

made with love, boba, and way too much libnvme API manual energy β€” this lil drop is from July 2026, mwah 😘🧚 βœ¨πŸŒΈπŸ’–πŸ¦‹πŸŽ€πŸ’…πŸ«Ά

πŸ“¦ where this page comes from