Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose bbr pacing_rate to users (incl. ffi) #1829

Open
mpelletan opened this issue Aug 2, 2024 · 1 comment
Open

Expose bbr pacing_rate to users (incl. ffi) #1829

mpelletan opened this issue Aug 2, 2024 · 1 comment

Comments

@mpelletan
Copy link

mpelletan commented Aug 2, 2024

Hello,

I'm using the library for a prototype but would like my application to limit how much data it feeds into the library for sending, in such a way that congestion (RTT increase, loss) is avoided, without incurring buffering into quiche's send buffer.

To do so I would need to be able to query the current pacing rate from the congestion control, but that's not currently exposed. I have a version of this change locally to unblock myself but proper support / consideration of any congestion control algorithm would of course be preferred. My version is a simple forwarding of the bbr2 state's pacing rate through path stats (and "null" if not using bbr).

Thanks!

@LPardue
Copy link
Contributor

LPardue commented Aug 2, 2024

This seems like something reasonable to expose in PathStats, we already record it in qlog but that's too late /awkward to be useful for anyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants