ntb_transport_tx_enqueue(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ntb_transport_tx_enqueue(9) 💅

okay bestie, welcome to the Kernel API Manual entry for ntb_transport_tx_enqueue(9) — yes, the whole manual name is folded right up here because we're doing this cute and correct. This page is literally about enqueueing a new NTB queue entry, and it's giving very specific kernel-queue energy. 🎀

🌸 NAME 🌸

ntb_transport_tx_enqueue — Enqueue a new NTB queue entry. That's the whole vibe. ✨

✨ SYNOPSIS ✨

int ntb_transport_tx_enqueue (struct ntb_transport_qp *qp , void *cb ,
       void *data , unsigned int len );

🎀 ARGUMENTS 🎀

  • qp — the NTB transport layer queue that this entry is to be enqueued on. Like, this is the queue, bestie. 👑
  • cb — a per buffer pointer for the callback function to use. It's not your main character; it's for the callback. 🦋
  • data — pointer to the data buffer that will be sent. The actual payload situation. 💖
  • len — length of the data buffer. Gotta know how much data is data-ing. 📏

🦋 DESCRIPTION 🦋

Enqueue a new transmit buffer onto the transport queue from which a NTB payload will be transmitted. That's the move: new transmit buffer, onto the transport queue, and that's where a NTB payload gets transmitted from. ✨

Heads up, bestie: this assumes that a lock is being held to serialize access to the qp. Not a vibe to ignore, okay? The page says it assumes the lock is held, so keep that in mind. 🔒💅

🔥 RETURN 🔥

An appropriate -ERRNO error value on error, or zero for success. So like: error means -ERRNO, success means zero. Slay when it's zero. 🫶

👑 SEE ALSO 👑

xoxo, your source/version ./drivers/ntb, dated October 2026 — ntb_transport_tx_enqueue(9) out 💖

📦 where this page comes from