From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>, libc-alpha@sourceware.org
Cc: nd@arm.com
Subject: Re: [PATCH 1/3] Guess L1 cache linesize for aarch64
Date: Tue, 10 Oct 2017 11:01:00 -0000 [thread overview]
Message-ID: <59DCA86E.2020405@arm.com> (raw)
In-Reply-To: <24591e6b-7da9-bd03-626c-6d4618e84da0@gotplt.org>
On 10/10/17 11:37, Siddhesh Poyarekar wrote:
> On Tuesday 10 October 2017 03:49 PM, Szabolcs Nagy wrote:
>> On 08/06/17 23:57, Richard Henderson wrote:
>>> + case _SC_LEVEL1_ICACHE_LINESIZE:
>>> + case _SC_LEVEL1_DCACHE_LINESIZE:
>>
>> i can't find documentation for these, what meaning do users expect?
>
> Applications may use these hints to try and align their code/data
> suitably or read/write data in an optimal manner. It needs to be
that's different from the given libgcc clear_cache example
> documented and I hope to have a patch ready for it soon, but I wanted to
> be sure that this patch was in place since otherwise the documentation
> does not make sense.
either there is existing meaning or it's a new api with
some proposed meaning, i wanted to look at that to tell
if the implementation is acceptable.
next prev parent reply other threads:[~2017-10-10 11:01 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 [this message]
2017-10-10 11:56 ` Siddhesh Poyarekar
2017-10-10 14:20 ` Richard Henderson
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=59DCA86E.2020405@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=siddhesh@gotplt.org \
/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).