ntb_transport_create_queue(9)

📦 version 7.3.1, in nixpkgs unstable

💖 ntb_transport_create_queue — NAME ✨

okay so this is ntb_transport_create_queue(9) from the Kernel API Manual, and it literally does what it says on the tin: Create a new NTB transport layer queue. bestie, that's it, that's the whole vibe 💅

🌸 SYNOPSIS 🌸

struct ntb_transport_qp * ntb_transport_create_queue (void *data ,
struct device *client_dev , const struct ntb_queue_handlers *handlers );

no cap, that's the whole call signature 🎀

🦋 ARGUMENTS 🦋

  • data — a pointer for callback data 🫶 like, this is the little bag of stuff your callbacks get handed back later, iykyk
  • client_dev — a struct device pointer ⭐
  • handlers — pointer to various ntb queue (callback) handlers 👑 this is where all your callback functions live

💜 DESCRIPTION 💜

so basically you're creating a new NTB transport layer queue, and while you're at it you're giving that queue a callback routine for both transmit and receive. two-for-one, obsessed 🌈

the receive callback routine will be used to pass up data when the transport has received it on the queue ✨ (like, incoming data goes up to you through it).

the transmit callback routine will be called when the transport has completed the transmission of the data on the queue and the data is ready to be freed 🔥 — so yes, that callback is your green light to free the data. main character energy for real 💀

🎀 RETURN 🎀

a pointer to the newly created ntb_queue, or NULL on error 😭 (check it, bestie, always check it).

🧚 SEE ALSO 🧚

fr fr, go touch grass after reading all those, but also read them, they're your friends 💖

okay that's the whole page!! this came from the ./drivers/ntb source, October 2026 edition, and it lives at ntb_transport_create_queue(9) — slay, you're done, go build something iconic 🦋👑

📦 where this page comes from