NVME_INIT_GET_LOG_PREDICTABLE_LAT_NVMSET-LIBNVME3(2)

πŸ“¦ version 3.2, in arch rolling

πŸ’… nvme_init_get_log_predictable_lat_nvmset(9) πŸ’…

okay so bestie, welcome to the libnvme API manual ✨ this one's a function page, and honestly? it's giving "small but mighty." let's get into it 🫢


🌸 NAME 🌸

nvme_init_get_log_predictable_lat_nvmset β€” Initialize passthru command for Predictable Latency Per NVM Set πŸŽ€

like, that's the whole vibe. it sets up your passthru command. that's it. that's the function. iconic behavior honestly πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

void nvme_init_get_log_predictable_lat_nvmset (struct
libnvme_passthru_cmd *cmd , __u16 nvmsetid , struct
nvme_nvmset_predictable_lat_log *log );

notice the void? yeah. it returns nothing. no status, no error code, no little "hey it worked" boolean. it just does the thing and dips 😭 so don't go looking for a return value, bestie, there isn't one ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • cmd β€” the passthru command you're gonna use. like, the actual command struct getting set up πŸ› οΈ
  • nvmsetid β€” the NVM set id. it's a __u16, so mind your types, ngl πŸ”’
  • log β€” the user address where the predictable latency log is gonna be stored πŸ“₯ literally where the data lands, so make sure it points somewhere real πŸ’€

πŸ”₯ DESCRIPTION πŸ”₯

so here's what it does, fr fr: it initializes the passthru command buffer for the Get Log command, and it does that with the LID value NVME_LOG_LID_PREDICTABLE_LAT_NVMSET πŸ‘‘

that's the whole plot. buffer β†’ initialized. LID β†’ set to NVME_LOG_LID_PREDICTABLE_LAT_NVMSET. predictable latency per NVM set β†’ unlocked. periodt πŸ’œ

no cap, the exact LID constant matters here β€” it's NVME_LOG_LID_PREDICTABLE_LAT_NVMSET, not some other log page. copy it exactly if you're checking your work 🧚

and that's the page, bestie! short, sweet, and honestly obsessed with how straightforward it is 🌈 no weird edge cases, no scary warnings, just a clean little init function doing its main character thing.

sign-off szn πŸŽ€ this gem comes to you from the libnvme API manual, dated October 2026, and the footer was out here looking like nvme_init_get_log_predictablenvme_init_ge...e_lat_nvmset(9) 😭 (yeah, the title got squished into the footer, we don't question the typesetting, we just vibe) πŸ’–βœ¨

πŸ“¦ where this page comes from