NVME_CTRL_SET_DISCOVERY_CTRL(2)
π nvme_ctrl_set_discovery_ctrl π
okay bestie, this one lives in the libnvme API manual (section 2, we love a syscall-adjacent moment β¨). It's literally one tiny function that flips one tiny flag, and honestly? iconic for that.
πΈ NAME πΈ
nvme_ctrl_set_discovery_ctrl β set the 'discovery_ctrl' flag π
π¦ SYNOPSIS π¦
void nvme_ctrl_set_discovery_ctrl (nvme_ctrl_t c , bool discovery );
π ARGUMENTS π
cβ the controller you're about to mess with, aka "Controller to be modified" πdiscoveryβ the value you're giving thediscovery_ctrlflag, no cap
β¨ DESCRIPTION β¨
So here's the tea β: this function sets the 'discovery_ctrl' flag in c, and that flag is the whole point β it tells you whether c connects to a discovery subsystem. That's it. That's the function. Short, sweet, main character energy ππ¦
heads up: it returns void, so don't go looking for a return value to obsess over. She gives nothing back and she's valid for that ππ
π«Ά sign-off π«Ά
That's the whole page, bestie β xoxo, from the libnvme API manual, dated July 2026 πβ go forth and set that flag π β¨
π¦ where this page comes from
- ubuntu stonking: libnvme-dev 1.16.2-1build1 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms