tb_tunnel_maximum_bandwidth(9)

📦 version 7.3.1, in nixpkgs unstable

✨ tb_tunnel_maximum_bandwidth(9) ✨

okay so bestie, welcome to the Kernel API Manual 💅 this one's a kernel function page, section 9, and it's literally called tb_tunnel_maximum_bandwidth — say that five times fast, I dare you 🫶

🌸 NAME 🌸

tb_tunnel_maximum_bandwidth — returns the maximum possible bandwidth 🎀 yes, that's the whole vibe. it tells you the biggest bandwidth number this tunnel could ever dream of (as long as nobody else is hogging it, more on that below 👀).

🔥 SYNOPSIS 🔥

int tb_tunnel_maximum_bandwidth (struct tb_tunnel *tunnel , int *max_up
, int *max_down );

that's it, that's the signature. no cap, just three little params and an int coming back at you 💖

🦋 ARGUMENTS 🦋

  • tunnel — the tunnel you're checking on 🧚 like, the main character here. this is the one getting the vibe check.
  • max_up — maximum upstream bandwidth in Mb/s ⬆️ literally the up number, in Mb/s.
  • max_down — maximum downstream bandwidth in Mb/s ⬇️ literally the down number, in Mb/s.

👑 RETURN 👑

  • the maximum possible bandwidth this tunnel can support — if it's not limited by other bandwidth clients 😭 (yes, "if". sharing is caring but sharing also caps your numbers, just saying).
  • -EOPNOTSUPP — if the tunnel does not support this function 💀 sorry bestie, this tunnel just doesn't do that.
  • -ENOTCONN — if the tunnel is not active 🙈 like, the tunnel is asleep, come back later.

🌈 SEE ALSO 🌈

kernel file ./drivers/thunderbolt/tunnel.c and honestly the whole friend group 🫶:

💡 lowkey the whole bandwidth saga is in that list — 'allocated', 'consumed', 'unused', 'reclaim' — it's giving bandwidth economy, fr fr.

and that's the page, bestie 🎀 tysm for reading. this one lives in ./drivers/thunderbolt, dated October 2026 — mwah, slay, periodt 💜✨

📦 where this page comes from