> I guess it's a pretty quiet week in kernel-hacker land. Must be,
> otherwise people would have better things to do than argue over KB
> vs. KiB. The alternative would be to conclude that significant
> portions of the lkml population prefer flaming to coding, and that
> couldn't possibly be the case, could it?
The kb versus KB versus KiB versus whatever may come next was always a
very flammable cause.
Now my opinion on this would be: By sticking KiB everywhere nothing is
helped. To the knowledgeable, it's nothing new that memory is measured
in binary units, while ethernet speed in decimal ones. To the newbie,
KiB is about as cryptical as KB and he'll never know which is which,
because as a newbie (s)he didn't read the standards.
And of course, every search-and-replace cleanup will always upset many
people regardless which direction it goes.
On the other hand, making documentation less ambiguous is always a good
thing. I'd suggest a more careful approach, adding descriptive wording
in places where bits and bytes may be confused, and where binary or
decimal prefixes may be.
And speaking of the 1 Mbps connection - I fear that in many cases
that'll be 1024000 bytes per second. What M is that? Binary or decimal?
Who does care?
-- Vojtech Pavlik SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/