LBLK-DIR-SEND(1)

✨ LBLK-DIR-SEND(1) ✨

okay bestie, gather round, we're looking at lblk-dir-send from the xNVMe manual pages 💖 (that's manual section 1, for the record, iykyk)

---

🌸 NAME 🌸

lblk-dir-send — Directive send for the given URI

---

🎀 SYNOPSIS 🎀

lblk dir-send <uri> [<args>]

---

🦋 DESCRIPTION 🦋

Directive send for the given URI

like. that's the whole vibe. you hand it a URI, it sends a directive. no cap. 💅

---

👑 REQUIRED 👑

• <uri> — the Device URI, bestie, it's mandatory, can't skip it 🙈 and it looks like one of these:
  • '/dev/nvme0n1'
  • '0000:01:00.1'
  • '10.9.8.1.8888'
  • '\.PhysicalDrive1'

---

✨ OPTIONAL ✨

all of these are optional, so like, use them if you need them, no pressure 🫶

• --nsid 0xNUM — Namespace Identifier for Command Construction
• --dspec 0xNUM — Directive specification associated with directive type
• --dtype 0xNUM — Directive type; Identify 0x0, Streams 0x1
• --doper 0xNUM — Directive operation to perform
• --endir 0xNUM — Directive enable/disable; Enable 0x1, Disable 0x0
• --tgtdir 0xNUM — Target directive to enable/disable
• --subnqn STRING — Subsystem NQN of the NVMe over Fabrics endpoint, e.g. 'nqn.2022-06.io.xnvme:ctrlnode1'
• --hostnqn STRING — The host NQN to use when connecting to NVMe over Fabrics controllers
• --be STRING — xNVMe backend, e.g. 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows'
• --dev-nsid 0xNUM — Namespace Identifier for Device Handle
• --admin STRING — xNVMe admin. command-interface, e.g. 'nvme', 'block'
• --mem STRING — xNVMe buffer/memory manager
• --direct NUM — Bypass layers
• --help — Show usage / help

---

💜 SEE ALSO 💜

Full documentation at: <https://xnvme.io/>

(go read it, it's giving main character energy fr fr 🔥)

---

🌈 AUTHOR 🌈

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung

---

and that's the whole page, bestie!! this one came out of the xNVMe manual, dated 09 September 2024 — go forth and send those directives, you absolute icon 💅✨🎀🦋💖