From: Andrew Pinski <pinskia@gmail.com>
To: Steve Ellcey <sellcey@mips.com>
Cc: Maxim Kuvyrkov <maxim@codesourcery.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
libc-ports@sourceware.org
Subject: Re: [PATCH] Optimize MIPS memcpy
Date: Mon, 15 Oct 2012 20:50:00 -0000 [thread overview]
Message-ID: <CA+=Sn1=SpqWumYfS52W8ccevSJ5Sc=c1vK1Fp_f1=NpJyav4FA@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1m0Y8rJ=NnoGwhNPRFF_R08+NO6pfu7j6ufz0g8XT-VSA@mail.gmail.com>
On Mon, Oct 15, 2012 at 1:42 PM, Andrew Pinski <pinskia@gmail.com> wrote:
> On Mon, Oct 15, 2012 at 1:34 PM, Steve Ellcey <sellcey@mips.com> wrote:
>> On Mon, 2012-10-15 at 13:20 -0700, Andrew Pinski wrote:
>>
>>> On:
>>> system type : EBB6300 (CN6335p2.1-1500-AAP)
>>> processor : 0
>>> cpu model : Cavium Octeon II V0.9
>>>
>>> I get:
>>> ...
>>> 0x200757cb, (no zeros)
>>> 0x200757cc, (no zeros)
>>> 0x200757cd, (no zeros)
>>> 0x200757ce, (no zeros)
>>> 0x200757cf, (0x20075780 to 0x20075800, 128 byte prefetch)
>>>
>>> Thanks,
>>> Andrew Pinski
>>
>> Andrew,
>>
>> Is there a macro I can/should use when building glibc/memcpy to know
>> that it should assume a Cavium Octeon with 128 byte prefetch instead of
>> the 32 byte prefetch?
>
>
> Building you could use __OCTEON__ but that does not change the fact
> you could build glibc for the standard mips32/mips64 and then not get
> a working glibc if it defaults to 32bytes prefetch.
Also it would be nice to use ifunc's like they are used on x86_64 (and
I think PPC also) so we can compile one generic version of glibc and
get the optimized version of memcpy. Though ifunc's have their own
issue as they don't currently work on MIPS (they cause internal linker
errors).
Thanks,
Andrew
>
> Thanks,
> Andrew Pinski
>
>>
>> Steve Ellcey
>> sellcey@mips.com
>>
>>
next prev parent reply other threads:[~2012-10-15 20:50 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 6:16 Maxim Kuvyrkov
2012-09-01 16:37 ` Joseph S. Myers
2012-09-03 9:12 ` Andrew T Pinski
2012-09-03 17:12 ` Maxim Kuvyrkov
2012-09-04 15:09 ` Steve Ellcey
2012-09-04 15:14 ` Carlos O'Donell
2012-09-04 17:03 ` Steve Ellcey
2012-09-04 17:28 ` Carlos O'Donell
2012-09-05 0:43 ` Maxim Kuvyrkov
2012-09-06 16:25 ` Steve Ellcey
2012-09-06 18:43 ` Roland McGrath
2012-09-06 19:37 ` Steve Ellcey
2012-09-07 21:24 ` Maxim Kuvyrkov
2012-09-11 4:35 ` Maxim Kuvyrkov
2012-09-11 15:18 ` Steve Ellcey
2012-09-20 9:05 ` Maxim Kuvyrkov
2012-09-20 18:38 ` Steve Ellcey
2012-09-28 3:48 ` Maxim Kuvyrkov
2012-10-06 4:43 ` Maxim Kuvyrkov
2012-10-08 17:04 ` Steve Ellcey
2012-10-08 22:31 ` Maxim Kuvyrkov
2012-10-09 20:50 ` Steve Ellcey
2012-10-15 17:49 ` Steve Ellcey
2012-10-15 20:20 ` Andrew Pinski
2012-10-15 20:34 ` Steve Ellcey
2012-10-15 20:42 ` Andrew Pinski
2012-10-15 20:50 ` Andrew Pinski [this message]
2012-10-15 21:36 ` Steve Ellcey
2012-10-15 21:47 ` Maxim Kuvyrkov
2012-10-17 17:30 ` Steve Ellcey
2012-10-29 18:00 ` Steve Ellcey
2012-10-29 18:03 ` Maxim Kuvyrkov
2012-10-30 7:16 ` Maxim Kuvyrkov
2012-10-30 7:19 ` Maxim Kuvyrkov
2012-10-30 17:46 ` Steve Ellcey
2012-10-30 21:56 ` Maxim Kuvyrkov
2012-10-30 22:19 ` Steve Ellcey
2012-12-19 1:51 ` Maxim Kuvyrkov
2012-12-19 16:59 ` Steve Ellcey
2012-10-31 19:27 ` Andreas Jaeger
2012-10-31 20:04 ` Steve Ellcey
2012-10-15 22:10 ` Joseph S. Myers
2012-10-15 21:29 ` Maciej W. Rozycki
2012-10-15 22:05 ` Maxim Kuvyrkov
2012-09-21 18:47 ` Steve Ellcey
2012-09-21 18:57 ` Joseph S. Myers
2012-09-21 20:41 ` [PATCH] Optimize MIPS memcpy (mips glibc test results) Steve Ellcey
2012-09-21 20:49 ` Joseph S. Myers
2012-09-21 20:56 ` Steve Ellcey
2012-09-21 19:12 ` [PATCH] Optimize MIPS memcpy Maxim Kuvyrkov
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='CA+=Sn1=SpqWumYfS52W8ccevSJ5Sc=c1vK1Fp_f1=NpJyav4FA@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=maxim@codesourcery.com \
--cc=sellcey@mips.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).