[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB6083D3C5616E60D3D03CCEB5FC3F2@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Mon, 1 Apr 2024 23:03:50 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: "Chatre, Reinette" <reinette.chatre@...el.com>
CC: "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>, "Yu, Fenghua"
<fenghua.yu@...el.com>, Peter Newman <peternewman@...gle.com>, James Morse
<james.morse@....com>, Babu Moger <babu.moger@....com>, Drew Fustini
<dfustini@...libre.com>, "x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"patches@...ts.linux.dev" <patches@...ts.linux.dev>
Subject: RE: [PATCH] Documentation/x86: Document resctrl bandwidth control
units are MiB
> It appears that there is no custom here and it may just be somebody's preference?
Reinette,
Thanks for digging around. I had thought there was general consensus that
memory was measured in 2^20, storage in 10^6 and networking in either
10^6 or 10^9 (but bits rather than bytes.
But, as you've found, there doesn't seem to be to be even that much of
a custom.
Maybe a case for https://xkcd.com/927/ (since it is April 1st, I propose
everyone standardize on Teranibbles per fortnight[1] :-) )
But back to the patch. As there is no standard, changing the documentation
to accurately represent the code looks like a good option.
-Tony
[1] 1 MiB/s == 2.5367 Tnibbles/fortnight
Powered by blists - more mailing lists