public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Tulio Magno Quites Machado Filho" <tuliom@linux.vnet.ibm.com>
To: Rajalakshmi Srinivasaraghavan <raji@linux.vnet.ibm.com>,
	libc-alpha@sourceware.org
Subject: Re: [PATCH] powerpc64: strchr/strchrnul optimization for power8
Date: Tue, 27 Dec 2016 19:56:00 -0000	[thread overview]
Message-ID: <87eg0t5epa.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1478592744-15714-1-git-send-email-raji@linux.vnet.ibm.com>

Rajalakshmi Srinivasaraghavan <raji@linux.vnet.ibm.com> writes:

> The P7 code is used for <=32B strings and for > 32B vectorized loops are used.
> This shows as an average 25% improvement depending on the position of search
> character.  The performance is same for shorter strings.
> Tested on ppc64 and ppc64le.
>
> 2016-11-08  Rajalakshmi Srinivasaraghavan  <raji@linux.vnet.ibm.com>
>
> 	* sysdeps/powerpc/powerpc64/multiarch/Makefile
> 	(sysdep_routines): Add strchr-power8 and strchrnul_power8.
> 	* sysdeps/powerpc/powerpc64/multiarch/ifunc-impl-list.c
> 	(strchr): Add __strchr_power8 to list of strchr functions.
> 	(strchrnul): Add __strchrnul_power8 to list of strchr functions.
> 	* sysdeps/powerpc/powerpc64/multiarch/strchr-power8.S: New file.
> 	* sysdeps/powerpc/powerpc64/multiarch/strchrnul-power8.S: New file.
> 	* sysdeps/powerpc/powerpc64/multiarch/strchr.c
> 	(strchr): Add __strchr_power8 to ifunc list.
> 	* sysdeps/powerpc/powerpc64/multiarch/strchrnul.c
> 	(__strchrnul): Add __strchrnul_power8 to ifunc list.
> 	* sysdeps/powerpc/powerpc64/power8/strchr.S: New file.
> 	* sysdeps/powerpc/powerpc64/power8/strchrnul.S: New file.

LGTM.

-- 
Tulio Magno

      reply	other threads:[~2016-12-27 19:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08  8:12 Rajalakshmi Srinivasaraghavan
2016-12-27 19:56 ` Tulio Magno Quites Machado Filho [this message]

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=87eg0t5epa.fsf@linux.vnet.ibm.com \
    --to=tuliom@linux.vnet.ibm.com \
    --cc=libc-alpha@sourceware.org \
    --cc=raji@linux.vnet.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).