libnvmf_con...e_discovered(9)

πŸ“¦ version 3.2, in arch rolling

πŸ’… libnvmf_con...e_discovered(9) πŸ’…

okay so bestie, this page is from the libnvme API manual, and it’s lowkey iconic for anyone poking at discovered controllers. ✨


🌸 NAME 🌸

libnvmf_config_resolve_discovered β€” parameters for a controller that is not in the configuration. no cap, that’s the whole vibe, periodt. πŸŽ€

✨ SYNOPSIS ✨

the signature is literally giving:

const struct libnvmf_params * libnvmf_config_resolve_discovered (const
struct libnvmf_config *config , const struct libnvmf_config_conn *via_dc
, bool is_dc );

πŸŽ€ ARGUMENTS πŸŽ€

  • config β€” the resolved configuration. main character of this whole call, fr fr.
  • via_dc β€” the DC connection the controller was discovered through, or NULL for a controller with no configured origin (e.g. an mDNS-discovered DC).
  • is_dc β€” true for a discovered discovery controller (a referral), false for a discovered I/O controller.

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so picture this: a controller learned at runtime β€” from a discovery log page, an AEN, or mDNS β€” has no section in the configuration, but still draws parameters from it: the defaults of the file scope it was discovered through, or the top-level scope when it has no configured origin. the four combinations are literally:

  • (via_dc = DC, is_dc = true) β€” a referral: a DC discovered via a DC; draws that DC's DC-defaults scope
  • (via_dc = DC, is_dc = false) β€” a DLP-discovered IOC; draws that DC's IOC-defaults scope
  • (via_dc = NULL, is_dc = true) β€” a DC with no configured origin (e.g. mDNS); draws the top-level DC scope
  • (via_dc = NULL, is_dc = false) β€” an IOC with no configured origin; draws the top-level IOC scope

πŸ’– RETURN πŸ’–

you get back a borrowed parameter set, valid while config is alive. via_dc must be a connection of config; an I/O-controller via_dc yields NULL. 🫢

bestie, Passing a connection that does not belong to config is undefined β€” do not do it. πŸ’€

mwah πŸ’‹ β€” this cutie is from the libnvme API manual, dated October 2026, and the footer tag is libnvmf_config_resolve_disclibnvmf_con...e_discovered(9). slay, byeee 🫢

πŸ“¦ where this page comes from