[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190222181316.GE10237@localhost.localdomain>
Date: Fri, 22 Feb 2019 11:13:17 -0700
From: Keith Busch <keith.busch@...el.com>
To: Brice Goglin <Brice.Goglin@...ia.fr>
Cc: linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
linux-mm@...ck.org, linux-api@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rafael Wysocki <rafael@...nel.org>,
Dave Hansen <dave.hansen@...el.com>,
Dan Williams <dan.j.williams@...el.com>
Subject: Re: [PATCHv6 06/10] node: Add memory-side caching attributes
On Fri, Feb 22, 2019 at 11:22:12AM +0100, Brice Goglin wrote:
> Le 14/02/2019 à 18:10, Keith Busch a écrit :
> > +What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/associativity
> > +Date: December 2018
> > +Contact: Keith Busch <keith.busch@...el.com>
> > +Description:
> > + The caches associativity: 0 for direct mapped, non-zero if
> > + indexed.
>
>
> Should we rename "associativity" into "indexing" or something else?
>
> When I see "associativity" that contains 0, I tend to interpret this as
> the associativity value itself, which would mean fully-associative here
> (as in CPU-side cache "ways_of_associativity" attribute), while actually
> 0 means direct-mapped (ie 1-associative) with yout semantics.
>
> Brice
Yes, that's a good suggestion.
Powered by blists - more mailing lists