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.

Sign up for GitHub

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

Jump to bottom

Bandwidth limiter APIs should use uint64_t not unsigned int #935

Open
azonenberg opened this issue Nov 6, 2024 · 1 comment
Open

Bandwidth limiter APIs should use uint64_t not unsigned int #935

azonenberg opened this issue Nov 6, 2024 · 1 comment
Labels
api API improvements cleanup Removing cruft
Milestone
v0.2

Comments

@azonenberg
Copy link
Collaborator

This prevents bandwidth limiters >4 GHz from being possible
@azonenberg azonenberg added this to the v0.2 milestone Nov 6, 2024
@azonenberg azonenberg added api API improvements cleanup Removing cruft labels Nov 6, 2024
@azonenberg
Copy link
Collaborator Author

EDIT: limit is in MHz so we're good for a while, but at least should be changed to uint32_t or another stdint type

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api API improvements cleanup Removing cruft
Projects
None yet
Milestone
v0.2
Development

No branches or pull requests
1 participant
@azonenberg