Nvtop: Nvidia GPU htop-like monitoring tool

this is correct. i'm a romanian and both schools and government use the octet. on the other hand private enterprise has long used the bit/byte and "octet" is nowadays mostly confusing people. but it goes a bit deeper than that and it's mostly due to french influences: language is considered at the heart of national identity [0]. this has been detrimental to developing a modern language. one of the effects is actually the slow death of languages that can't adapt to their surroundings. instead we get english words translated in a crude manner to romanian or french. words that no one uses as the english/american versions are not only more popular, but also much more flexible. the french (romanians and others) are highly protective of their language, which is why they're losing the language battles.

[0] https://www.theguardian.com/commentisfree/2013/may/23/langua...

Yes, but Mo is more technically correct where "byte = 8 bits" is merely "de facto" correct. There were (likely still are) designs with bytes of 6, 7, 9 and other numbers of bits, where octet an is always 8 bits.

Then again if we cared for "technically correct" as much as we claim to when correcting other people, we'd use KiB/MiB/... instead of MB/KB/... when working in 1024s not 1000s!

My understanding of byte is that it is defined as "the smallest unit other than a single bit that a processing unit naturally deals with". Similarly "word" is the largest value the instruction set natively deals with (i.e. the architecture's register size).

Obviously these definitions are only general and are "broken" by many exceptions: for instance many CISC designs with 8-bit bytes have some instructions that work on data in 4-bit chunks (nibbles/nybbles), multiply instructions need to output twice the input size to be efficiently useful, and so on. Also "word" has in some places become synonymous with 32-bits rather than its more general definition, in much the same way "byte" became so with 8-bits.