LIBNVME_CTRL_GET_TLS_KEY_ID-LIBNVME3(2)
π libnvme_ctrl_get_tls_key_id(9) π
okay bestie so this is a page straight out of the libnvme API manual (section 9, section 9 things, you know the vibe β¨) and honestly it's a short one but it's cute and it does exactly one thing, so let's get into it π«Ά
β¨ NAME β¨
libnvme_ctrl_get_tls_key_id β get that tls_key_id, that's it, that's the whole job π
πΈ SYNOPSIS πΈ
long libnvme_ctrl_get_tls_key_id (const struct libnvme_ctrl *p );
like, look at her. one argument, returns a long. she's not doing too much and honestly? iconic π
π ARGUMENTS π
pβ thestruct libnvme_ctrlinstance you wanna query, aka the controller you're being nosy about π (and yeah it'sconst, so no, you're not allowed to touch her, only look β)
β RETURN β
she hands you back the value of the tls_key_id field, that's the whole plot π it's a long, it's the field's value, no cap, no surprises, no little tricks β just the number you asked for π
π¦ SEE YOU LATER π¦
that's genuinely the entire page, bestie β no options, no env vars, no caveats, no scary warnings, just one tiny getter living her best life π§
ngl if this is the whole manpage you're reading, go drink some water and then go read the actual struct docs, iykyk ππ
this little gem is from the libnvme API manual, dated October 2026, and it was brought to you by libnvme_ctrl_get_tls_key_id(9) β mwah, go slay your TLS keys ππβ¨
π¦ where this page comes from
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms