lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160708193457.GA18734@gmail.com>
Date:	Fri, 8 Jul 2016 21:34:57 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Borislav Petkov <bp@...e.de>
Cc:	"Luck, Tony" <tony.luck@...el.com>,
	"Yu, Fenghua" <fenghua.yu@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"Anvin, H Peter" <h.peter.anvin@...el.com>,
	Ingo Molnar <mingo@...e.hu>,
	Stephane Eranian <eranian@...gle.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Vikas Shivappa <vikas.shivappa@...ux.intel.com>,
	"Shankar, Ravi V" <ravi.v.shankar@...el.com>,
	linux-kernel <linux-kernel@...r.kernel.org>, x86 <x86@...nel.org>
Subject: Re: [PATCH v2 2/3] Documentation, ABI: Add a document entry for
 cache id


Yeah, so if the 'cache index' naming has already been settled, then I suspect 
we'll have to live with it - but at least let's name it 'cache-index' when we 
refer to it, not just 'index' which is super confusing (to me!).

I.e. instead:

  The id identifies a cache in the platform. In same index, the id
  is unique across the platform.

Something like this is more readable I think:

  The cache-id identifies a hardware cache of the system within a given
  cache-index category of caches. The (cache-index,cache-id) pair is
  unique for the whole system.

agreed?

Thanks,

	Ingo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ