From: Michael Jeanson <mjeanson@efficios.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH v7 0/8] Extend rseq support
Date: Fri, 2 Feb 2024 10:40:56 -0500 [thread overview]
Message-ID: <1eb3ad80-a52f-4176-bc6b-836528c84c48@efficios.com> (raw)
In-Reply-To: <20240201193648.584917-1-mjeanson@efficios.com>
On 2024-02-01 14:36, Michael Jeanson wrote:
> This series rebases the standalone "Add rseq extensible ABI" patch on
> current master and adds an accelerated getcpu() implementation using the
> rseq extensible ABI with initial support for aarch64 and x86_64.
>
> On an aarch64 system (Snapdragon 8cx Gen 3) which lacks a vDSO for
> getcpu() we measured an improvement from 130 ns to 1 ns while on x86_64
> (i7-8550U) which has a vDSO we measured a more modest improvement from
> 10 ns to 2 ns.
>
> Tested on i386, aarch64 and x86_64.
The failures reported by the Linaro-TCWG-CI on arm seem to be only an issue of
symbol sorting in the abilist files. Is there tooling to regenerate those for
all architectures?
Thanks,
Michael
next prev parent reply other threads:[~2024-02-02 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 19:36 Michael Jeanson
2024-02-01 19:36 ` [PATCH v7 1/8] nptl: fix potential merge of __rseq_* relro symbols Michael Jeanson
2024-02-01 19:36 ` [PATCH v7 2/8] Add rseq extensible ABI support Michael Jeanson
2024-02-01 19:36 ` [PATCH v7 3/8] nptl: Add public __rseq_feature_size symbol Michael Jeanson
2024-02-01 19:36 ` [PATCH v7 4/8] nptl: Add features to internal 'struct rseq_area' Michael Jeanson
2024-02-01 19:36 ` [PATCH v7 5/8] nptl: Add rseq internal utils Michael Jeanson
2024-02-01 19:36 ` [PATCH v7 6/8] x86-64: Add rseq_load32_load32_relaxed Michael Jeanson
2024-02-01 19:36 ` [PATCH v7 7/8] aarch64: " Michael Jeanson
2024-02-01 19:36 ` [PATCH v7 8/8] Linux: Use rseq to accelerate getcpu Michael Jeanson
2024-02-02 15:40 ` Michael Jeanson [this message]
2024-02-02 16:18 ` [PATCH v7 0/8] Extend rseq support Adhemerval Zanella Netto
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=1eb3ad80-a52f-4176-bc6b-836528c84c48@efficios.com \
--to=mjeanson@efficios.com \
--cc=libc-alpha@sourceware.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).