libnvme_get...ynamic_chunk(9)

📦 version 3.2, in arch rolling

libnvme_get_log_dynamic_chunk(9) 🦋

Okay bestie, welcome to libnvme_get_log_dynamic_chunk(9)</p> from the libnvme API manual — it's literally about getting log page data with a dynamic chunk size, and it's giving very smart-girl energy 💅✨

NAME 🎀

libnvme_get_log_dynamic_chunk — get log page data with dynamic chunk size 🌸

SYNOPSIS 💖

int libnvme_get_log_dynamic_chunk (struct libnvme_transport_handle *hdl
, struct libnvme_passthru_cmd *cmd , bool rae , __u32 xfer_len );

ARGUMENTS 🫶

  • hdl — transport handle
  • cmd — passthru command
  • rae — retain asynchronous events
  • xfer_len — initial max log transfer size per request to split the total. The way this works is dynamically divide chunk size by 2 when any error is encountered, and retry until the chunk size is down to 4k or the command succeeds. This allows for successful retrieval of log pages that may have a smaller maximum transfer size than the controller's MDTS value, without requiring the caller to know the optimal chunk size in advance 👑

RETURN 💀

0 on success ✨, the nvme command status if a response was received (see enum nvme_status_field) 👀, or a negative error otherwise 😭

k bye bestie 💋 — this page is from the libnvme API manual, October 2026 edition, with footer source/version tea libnvme_get_log_dynamic_clibnvme_get...ynamic_chunk(9) — periodt 💅🌈

📦 where this page comes from