nvme_get_log_host_discover(2)

πŸ’– nvme_get_log_host_discover(2) πŸ’–

okay bestie, welcome to the libnvme API manual, section 2 β€” this one's all about nvme_get_log_host_discover, and yes she's a whole function, not just a vibe. let's get into it 🫢


✨ NAME ✨

nvme_get_log_host_discover β€” Retrieve Host Discovery Log 🌸

like... it goes and gets the Host Discovery Log. that's the whole job. she's employed, she's thriving, periodt. πŸ‘‘


✨ SYNOPSIS ✨

int nvme_get_log_host_discover (int fd , bool allhoste , bool rae ,
       __u32 len , struct nvme_host_discover_log *log );

look at her signature, so clean, so iconic ✨ return type int, five lil params, no drama. πŸ’…


✨ ARGUMENTS ✨

  • fd β€” the file descriptor of the nvme device. that's your ticket in, bestie, no fd no entry 🎟️
  • allhoste β€” all host entries. yes the spelling is allhoste, we do not ask questions, we type it exactly like that 😭
  • rae β€” retain asynchronous events. keep those events around, she's a keeper πŸ¦‹
  • len β€” the allocated length of the log page. how much room you set aside for the whole thing πŸ“
  • log β€” user address to store the log page. this is where the goodies land when it's done πŸŽ€

✨ RETURN ✨

okay so what do you get back? either:

  • the nvme command status if a response was received β€” peep enum nvme_status_field for the deets πŸ‘€
  • or -1 with errno set otherwise πŸ’€

literally that's it. no cap. 🌈


heads up bestie: if you get a -1, go check errno before you spiral β€” she's telling you what went wrong fr fr πŸ™ˆ

and that's the page!! mwah πŸ’œ stay slay, read your man pages, and remember: every flag matters, every detail stays, we don't skip a single one in this house 🏠✨

this was nvme_get_log_host_discover(2) from the libnvme API manual, dated July 2026 β€” xoxo, your fav unix girly πŸ’–πŸŽ€

πŸ“¦ where this page comes from