Re:RISC-V OS using Rust: Filesystems
by pavehawk2007 on Tuesday May 12, 2020 @03:34PM
(#23158637)
If that irritates you, please don't check the grammar and errant placement of commas!
All jokes aside. Fixed, thanks.
Re:RISC-V OS using Rust: Filesystems
by a1369209993 on Tuesday May 12, 2020 @03:44PM
(#23158777)
Actually, the grammar seems fine? Or at least I haven't noticed any problems with it. TFA as a whole seems pretty good actually. The file sizes are still incorrect, though; it calls the units kilobytes now, but it still claims there's 262 of them.
The seven blocks at the start would make it 263 KB, but I don't think that what you meant.
>The file sizes are still incorrect, though; it calls the units kilobytes now, but it still claims there's 262 of them.
1024 * 1024 / 4 B = 262144 B = 262.144 KB = 256 KiB
Re:RISC-V OS using Rust: Filesystems
by a1369209993 on Tuesday May 12, 2020 @08:42PM
(#23162055)
Yes, exactly; 262144 bytes is 256 kilobytes.
Re:RISC-V OS using Rust: Filesystems
by GolDDranks on Tuesday May 12, 2020 @10:01PM
(#23162623)
262144 bytes; 262144 / 1024 = 256 kibibytes
262144 bytes; 262144 / 1000 ≈ 262 kilobytes
KB is kilobyte. KiB is kibibyte.
> kibibyte
I wonder if anyone uses this abomination of a word in real life though.
Re:RISC-V OS using Rust: Filesystems
by a1369209993 on Tuesday May 12, 2020 @11:30PM
(#23163185)
Not that I know of; they're called kilobytes.
Re:RISC-V OS using Rust: Filesystems
by a1369209993 on Tuesday May 12, 2020 @09:26PM
(#23162378)
Yes, KB = kilobyte = 1024 byte.
At this point I can only assume I'm being trolled.
This whole thread is confusing to me as well. Isn't the whole point of a kibibyte to work in increments of 1024, unlike kilo, which is actually 1000, as defined by the sciences long ago?
So 1024 * 256 is 256 KiB by definition, since a Kibibyte is literally 1024 bytes, and the number of Kilobytes will by higher, since the number it represents is smaller.
Re:RISC-V OS using Rust: Filesystems
by GolDDranks on Wednesday May 13, 2020 @02:22AM
(#23164034)
Either user a1369209993 is unaware of the distinction ( https://en.wikipedia.org/wiki/Kibibyte ) or then they are deliberately ignoring it (My guess: to defend the old definition of kilobyte = 1024 bytes) to the point that their messages look like trolling.
Reality will forcibly catch up with them when they try to buy a new harddrive.
Re:RISC-V OS using Rust: Filesystems
by pavehawk2007 on Wednesday May 13, 2020 @10:07AM
(#23166999)
That's what I thought. I really only care about how much "stuff" I can store in a block, which is 1,024 bytes. If that's 1KiB or 1.024KBs, the distinction isn't worth that much brainpower.
Re:RISC-V OS using Rust: Filesystems
by jfkebwjsbx on Wednesday May 13, 2020 @03:38AM
(#23164464)
It is actually 256 KiB, not KB.
> The singly-indirect pointer can address 1,024 * 1,024 / 4 = 1,024 * 256 = 262 KiB of data.
256 kilobytes, not 262 'kibi'bytes.
> 1,024 * 256 * 256 = 67 Mi
> 1,024 * 256 * 256 * 256 = 17 Gi
64 and 16 respectively.