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

doc: limit-rate clarify base unit #7439

Closed
jsoref opened this issue Jul 19, 2021 · 3 comments
Closed

doc: limit-rate clarify base unit #7439

jsoref opened this issue Jul 19, 2021 · 3 comments

Comments

@jsoref
Copy link
Contributor

@jsoref jsoref commented Jul 19, 2021

Appending 'k' or 'K' will count the number as kilobytes, 'm' or 'M' makes it
megabytes, while 'g' or 'G' makes it gigabytes. Examples: 200K, 3m and 1G.

I presume that this k is 2^10, but Wikipedia pretends it means 10^3. (I'm not endorsing this notation, but docs should be clear.)

@bagder
Copy link
Member

@bagder bagder commented Jul 19, 2021

They're all 1024-based. So K is 1024, M is 1024 * 1024 and G is 1024 * 1024 * 1024.

@jsoref
Copy link
Contributor Author

@jsoref jsoref commented Jul 19, 2021

I don't have prose and I'm not sure how many places should mention it, but this seems like a place that should include it. Happy to talk it out online.

@jsoref
Copy link
Contributor Author

@jsoref jsoref commented Jul 20, 2021

second. The suffixes (k, M, G, T, P) are 1024 based. For example 1k is 1024

jsoref added a commit to jsoref/curl that referenced this issue Jul 25, 2021
closes curl#7439
@bagder bagder closed this in b045a7d Jul 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

2 participants