tb_tunnel_a...ed_bandwidth(9)

💖 NAME 💖

tb_tunnel_allocated_bandwidth — return bandwidth allocated for the tunnel. That's the whole assignment, bestie: you check the tunnel and it tells you how much bandwidth it's been allocated. Straight from the Kernel API Manual, page tb_tunnel_a...ed_bandwidth(9), and yes it's giving very specific thunderbolt energy ✨

✨ SYNOPSIS ✨

int tb_tunnel_allocated_bandwidth (struct tb_tunnel *tunnel , int *allocated_up , int *allocated_down );

🎀 ARGUMENTS 🎀

• tunnel — tunnel to check. Like, which tunnel are we looking at? 👀
• allocated_up — currently allocated upstream bandwidth in Mb/s is stored here. It writes through this pointer, so don't hand it nonsense, fr fr.
• allocated_down — currently allocated downstream bandwidth in Mb/s is stored here. Same situation, but downstream edition 💅

💅 RETURN 💅

• Bandwidth allocated for the tunnel. This may be higher than what the tunnel actually consumes. (iconic over-allocation moment, no cap 🔥)
• -EOPNOTSUPP — if the tunnel does not support this function.
• -ENOTCONN — if the tunnel is not active.
• Negative errno — another error occurred.

🦋 SEE ALSO 🦋

Kernel file: ./drivers/thunderbolt/tunnel.c — and the whole squad is:

• tb_available_credits(9)
• tb_tunnel_event(9)
• tb_tunnel_discover_pci(9)
• tb_tunnel_alloc_pci(9)
• tb_tunnel_reserved_pci(9)
• tb_dp_bandwidth_mode_maximum_bandwidth(9)
• tb_tunnel_discover_dp(9)
• tb_tunnel_alloc_dp(9)
• tb_tunnel_alloc_dma(9)
• tb_tunnel_match_dma(9)
• tb_tunnel_discover_usb3(9)
• tb_tunnel_alloc_usb3(9)
• tb_tunnel_is_invalid(9)
• tb_tunnel_activate(9)
• tb_tunnel_deactivate(9)
• tb_tunnel_port_on_path(9)
• tb_tunnel_maximum_bandwidth(9)
• tb_tunnel_alloc_bandwidth(9)
• tb_tunnel_consumed_bandwidth(9)
• tb_tunnel_release_unused_bandwidth(9)
• tb_tunnel_reclaim_available_bandwidth(9)

mwah 💋 this little page was served from ./drivers/thunderbolt, dated October 2026 — catch you in the next manpage, bestie 🫶🌸