tb_tunnel_co...ed_bandwidth(9)

📦 version 7.3.1, in nixpkgs unstable

🌈 tb_tunnel_consumed_bandwidth — from the Kernel API Manual (9) ✨

okay bestie, so this one's a kernel API page, section 9, and it's literally called tb_tunnel_consumed_bandwidth. we're in drivers/thunderbolt land and honestly? it's giving "small function, big feelings." 🦋

✨ NAME ✨

tb_tunnel_consumed_bandwidth — returns the bandwidth that a tunnel is consuming 💅

🌸 SYNOPSIS 🌸

int tb_tunnel_consumed_bandwidth (struct tb_tunnel *tunnel , int
*consumed_up , int *consumed_down );

🎀 ARGUMENTS 🎀

  • tunnel — the tunnel you wanna check, bestie. that's the main character right there 👑
  • consumed_up — consumed bandwidth in Mb/s, going from dst_port to src_port. can be NULL 🫶
  • consumed_down — consumed bandwidth in Mb/s, going from src_port to dst_port. can also be NULL 🫶

💖 DESCRIPTION 💖

so what it does is, it stores the amount of isochronous bandwidth the tunnel consumes into consumed_up and consumed_down. that's it, that's the vibe. no cap, it just fills those two out for you ✨

⭐ RETURN ⭐

0 on success, and a negative errno otherwise. lowkey iconic, highkey predictable 😭

🦋 SEE ALSO 🦋

the kernel file lives at ./drivers/thunderbolt/tunnel.c and here's the whole friend group, no one left behind fr fr:

reminder bestie: those two int * out-params can be NULL and that's totally fine, the function still slays 💀

and that's the page!! source is ./drivers/thunderbolt, dated October 2026, manual name tb_tunnel_co...ed_bandwidth(9) — mwah, go read some more kernel docs, ily 🧚💜🎀

📦 where this page comes from