From: Richard Henderson <rth@twiddle.net>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>, libc-alpha@sourceware.org
Cc: nd@arm.com, Marcus Shawcroft <marcus.shawcroft@arm.com>
Subject: Re: [PATCH 1/3] Guess L1 cache linesize for aarch64
Date: Tue, 10 Oct 2017 14:20:00 -0000 [thread overview]
Message-ID: <8fc9a891-aa77-2578-d450-1217c568e21c@twiddle.net> (raw)
In-Reply-To: <59DC9EC6.5080606@arm.com>
On 10/10/2017 03:19 AM, Szabolcs Nagy wrote:
> On 08/06/17 23:57, Richard Henderson wrote:
>> + /* Unfortunately, the registers that contain the actual cache info
>> + (CCSIDR_EL1, CLIDR_EL1, and CSSELR_EL1) are protected by the Linux
>> + kernel (though they need not have been). However, CTR_EL0 contains
>> + the *minimum* linesize in the entire cache hierarchy, and is
>> + accessible to userland, for use in __aarch64_sync_cache_range,
>> + and it is a reasonable assumption that the L1 cache will have that
>> + minimum line size. */
>
> maybe
Have you ever seen a system for which this was not true?
I don't believe I have.
>> + case _SC_LEVEL1_ICACHE_LINESIZE:
>> + case _SC_LEVEL1_DCACHE_LINESIZE:
>
> i can't find documentation for these, what meaning do users expect?
They expect them to be exactly what they say they are.
The question is, what do they expect to be able to do with that information.
Speaking for myself, I expect to be able to dynamically align objects on this
linesize and for that to have some predictable effect on performance.
r~
next prev parent reply other threads:[~2017-10-10 14:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 22:57 [PATCH 0/3] Add some missing cache infomation Richard Henderson
2017-06-08 22:57 ` [PATCH 1/3] Guess L1 cache linesize for aarch64 Richard Henderson
2017-06-09 5:51 ` Siddhesh Poyarekar
2017-06-09 5:52 ` Andrew Pinski
2017-10-10 7:24 ` Siddhesh Poyarekar
2017-10-10 10:20 ` Szabolcs Nagy
2017-10-10 10:37 ` Siddhesh Poyarekar
2017-10-10 11:01 ` Szabolcs Nagy
2017-10-10 11:56 ` Siddhesh Poyarekar
2017-10-10 14:20 ` Richard Henderson [this message]
2017-10-11 5:28 ` Siddhesh Poyarekar
2017-10-10 17:19 ` Szabolcs Nagy
2017-06-08 22:57 ` [PATCH 3/3] Add cache info for powerpc64 Richard Henderson
2017-06-09 6:59 ` Florian Weimer
2017-06-09 13:12 ` Tulio Magno Quites Machado Filho
2017-06-09 20:07 ` Richard Henderson
2017-06-08 22:57 ` [PATCH 2/3] Add hidden_proto for getauxval Richard Henderson
2017-06-09 5:55 ` Siddhesh Poyarekar
2017-06-09 6:58 ` Florian Weimer
2017-06-09 17:45 ` Richard Henderson
2017-06-09 17:49 ` Florian Weimer
2017-06-09 22:11 ` Richard Henderson
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=8fc9a891-aa77-2578-d450-1217c568e21c@twiddle.net \
--to=rth@twiddle.net \
--cc=libc-alpha@sourceware.org \
--cc=marcus.shawcroft@arm.com \
--cc=nd@arm.com \
--cc=szabolcs.nagy@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).