linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
	linux-man@vger.kernel.org, benh@kernel.crashing.org,
	mpe@ellerman.id.au
Subject: Re: [PATCH] getauxval.3: Add new cache geometry entries
Date: Wed, 25 Sep 2019 04:41:59 +1000	[thread overview]
Message-ID: <20190924184158.3f3au7aqnitasrrn@localhost.localdomain> (raw)
In-Reply-To: <91faffae-777b-7e77-2986-463dc01508be@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]

At 2019-09-23T10:36:16-0300, Raphael M Zinsly wrote:
> > > +Geometry of the L1 data cache, that is, line size and number
> > > +of ways.
> > 
> > What is "number of ways"?
> 
> It is the cache associativity, e.g.: 8 means the cache is 8-way set
> associative.

Yup.  At some point when I wasn't looking, the "-way" in "n-way cache"
got promoted from a partial adjective along the lines of "all cars must
halt at the four-way stop sign" to a full-blooded noun and term of art.
I bumped into it while proofreading a Ph.D. thesis[1].

To help familiarize practitioners with the new cloak of terminology
draped over this hoary descendant of Old English "weg", I suggest adding
a parenthetical:

  Geometry of the L1 data cache; that is, line size and number of ways
  (e.g., \(lq4-way associative\(rq).

Regards,
Branden

[1] Ge, Qian, "Mitigating Microarchitecture-based Timing Channels with
Lightweight Operating System Mechanisms", Ph.D. thesis, University of
New South Wales, in press.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-09-24 18:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 18:41 [PATCH] getauxval.3: Add new cache geometry entries Raphael Moreira Zinsly
2019-09-23 12:27 ` Michael Kerrisk (man-pages)
2019-09-23 13:36   ` Raphael M Zinsly
2019-09-24 18:41     ` G. Branden Robinson [this message]
2019-09-24 20:08       ` Michael Kerrisk (man-pages)
2019-09-24  4:27 ` Michael Kerrisk (man-pages)
2019-09-24 13:11   ` [PATCH v2] " Raphael Moreira Zinsly
2019-09-24 20:05     ` Michael Kerrisk (man-pages)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190924184158.3f3au7aqnitasrrn@localhost.localdomain \
    --to=g.branden.robinson@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=mtk.manpages@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).