libnvme API review

Tue Mar 17 08:05:21 PDT 2026

On Tue, Mar 17, 2026 at 10:26:28AM +0100, Daniel Wagner wrote:
> The only way I currently see to resolve this is by using a different
> prefix for the library APIs (e.g., libnvme_) and reserving the nvme_
> prefix exclusively for NVMe spec APIs. However, I am unsure if this
> approach will reach a consensus here.

I think such a split would be immensely useful, not matter what the
final prefixes are.  The "nvme" tool has similar issues with a mix of
actual nvme command and calls to the kernel or other functionality.