public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Cc: tuliom@linux.ibm.com,  rzinsly@linux.ibm.com,  anton@ozlabs.org
Subject: Re: [PATCH v2] powerpc64le: Optimize memset for POWER10
Date: Fri, 30 Apr 2021 14:21:04 +0200	[thread overview]
Message-ID: <87zgxg55fz.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20210430121633.kqfheh2tidgyiyap@work-tp> (Raoni Fassina Firmino's message of "Fri, 30 Apr 2021 09:16:33 -0300")

* Raoni Fassina Firmino:

> On Fri, Apr 30, 2021 at 06:52:42AM +0200, AL glibc-alpha wrote:
>> * Raoni Fassina Firmino via Libc-alpha:
>> 
>> > +L(dcbz_loop):
>> > +	/* Sets 512 bytes to zero in each iteration, the loop unrolling shows
>> > +	   a throughput boost for large sizes (2048 bytes or higher).  */
>> > +	dcbz	0,r6
>> > +	dcbz	r9,r6
>> > +	dcbz	r10,r6
>> > +	dcbz	r11,r6
>> > +	addi	r6,r6,512
>> > +	bdnz	L(dcbz_loop)
>> 
>> > +# ifdef __LITTLE_ENDIAN__
>> > +	    (hwcap2 & (PPC_FEATURE2_ARCH_3_1 | PPC_FEATURE2_HAS_ISEL)
>> > +	     && hwcap & PPC_FEATURE_HAS_VSX)
>> > +	    ? __memset_power10 :
>> > +# endif
>> 
>> Should the IFUNC resolver check that the cache line size is 128 bytes?
>
> I'm not sure, this part was taken from power8 version and for that it
> does not check the cache line size.  In fact I looked all other memset
> versions (power7, power6, power4 and ppc), and only the ppc version does
> not assume a 128 bytes cache line.  And none has this check (and all of
> them uses dcbz).  So I don't know.

Hmm, you are right, I think we had a discussion about this already (in
the POWER8 context) because the string function breaks if the cache line
size (as emulated by QEMU, if I recall correctly) are unexpected.

Thanks,
Florian


  reply	other threads:[~2021-04-30 12:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 23:45 Raoni Fassina Firmino
2021-04-30  4:52 ` Florian Weimer
2021-04-30 12:16   ` Raoni Fassina Firmino
2021-04-30 12:21     ` Florian Weimer [this message]
2021-04-30 12:23       ` Florian Weimer
2021-04-30 13:02 ` Matheus Castanho
2021-04-30 21:15 ` Tulio Magno Quites Machado Filho

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=87zgxg55fz.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=anton@ozlabs.org \
    --cc=libc-alpha@sourceware.org \
    --cc=rzinsly@linux.ibm.com \
    --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).