From: Tulio Magno Quites Machado Filho via Libc-alpha <libc-alpha@sourceware.org>
To: Anton Blanchard <anton@ozlabs.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 2/3] powerpc64: Check cacheline size before using optimised memset routines
Date: Fri, 06 Aug 2021 16:50:17 -0300 [thread overview]
Message-ID: <87eeb6cpza.fsf@linux.ibm.com> (raw)
In-Reply-To: <20210727054751.3972562-2-anton@ozlabs.org>
Anton Blanchard via Libc-alpha <libc-alpha@sourceware.org> writes:
> A number of optimised memset routines assume the cacheline size is 128B,
> so we better check before using them.
LGTM.
The patch is still missing the changes for bzero(), but I understand this is
already an improvement over what we had.
I plan to modify bzero later.
Pushed as f2a15dd668913c5a1388ba7e1131b25162b2ea75.
Thanks!
--
Tulio Magno
next prev parent reply other threads:[~2021-08-06 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 5:47 [PATCH 1/3] powerpc64: Replace some PPC_FEATURE_HAS_VSX with PPC_FEATURE_ARCH_2_06 Anton Blanchard via Libc-alpha
2021-07-27 5:47 ` [PATCH 2/3] powerpc64: Check cacheline size before using optimised memset routines Anton Blanchard via Libc-alpha
2021-08-06 19:50 ` Tulio Magno Quites Machado Filho via Libc-alpha [this message]
2021-07-27 5:47 ` [PATCH 3/3] powerpc64: Add checks for Altivec and VSX in ifunc selection Anton Blanchard via Libc-alpha
2021-08-06 19:50 ` Tulio Magno Quites Machado Filho via Libc-alpha
2021-08-06 19:48 ` [PATCH 1/3] powerpc64: Replace some PPC_FEATURE_HAS_VSX with PPC_FEATURE_ARCH_2_06 Tulio Magno Quites Machado Filho via Libc-alpha
-- strict thread matches above, loose matches on Subject: below --
2021-07-06 10:51 Anton Blanchard via Libc-alpha
2021-07-06 10:51 ` [PATCH 2/3] powerpc64: Check cacheline size before using optimised memset routines Anton Blanchard via Libc-alpha
2021-07-08 22:33 ` Tulio Magno Quites Machado Filho via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eeb6cpza.fsf@linux.ibm.com \
--to=libc-alpha@sourceware.org \
--cc=anton@ozlabs.org \
--cc=tuliom@linux.ibm.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).