From: "Gérard Guével" <gguevel@interfaceconcept.com>
To: "'Andy Fleming'" <afleming@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: How to use SPE on MPC8541
Date: Wed, 28 Sep 2005 10:02:18 +0200 [thread overview]
Message-ID: <003201c5c402$fb80d430$5201a8c0@GEG2400> (raw)
In-Reply-To: <B310BDDC-A773-4D85-8314-F4320C5FA90C@freescale.com>
Andy,
> Your driver runs in kernel space. The kernel has the SPE bit off.
> The MSR state is process-specific. If the code executes, the
> MSR bit
> is set. Why do you want to see if the bit is set?
OK, this is a bad idea to use a driver to check the msr register.
I don't especially want to see if the bit is set, I just want
to improve the board performance for a Linux application :-).
To check the performance, I used the Dhrystone 2.1 benchmark with
the standard glibc (strcpy, strcmp, ...) on one part, and with
the freescale SPE library on the other part (vstrcpy, vstrcmp, ...).
I already verified in the binary elf file that the right functions are
called.
When I run the benchmark, I get the same MIPS with and without SPE code.
I ran the same benchmark on the same board without OS,
with a personal pseudo glibc, I have the same MIPS as under Linux,
with the freescale library, I gain 40% of perf.
That's I want to retreive with the Linux OS.
Regards
Gérard
next prev parent reply other threads:[~2005-09-28 7:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 17:46 Linux Kernel Issue: MPC8540 Errata (CPU29) Chiradeep Vittal
2005-04-27 18:36 ` Kumar Gala
2005-09-27 15:30 ` How to use SPE on MPC8541 Gérard Guével
2005-09-27 15:56 ` Andy Fleming
2005-09-27 17:36 ` Gérard Guével
2005-09-27 18:50 ` Andy Fleming
2005-09-28 8:02 ` Gérard Guével [this message]
2005-09-28 15:32 ` Andy Fleming
2005-09-29 13:23 ` Gérard Guével
-- strict thread matches above, loose matches on Subject: below --
2005-09-28 8:12 Fillod Stephane
2005-09-28 15:34 ` Andy Fleming
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='003201c5c402$fb80d430$5201a8c0@GEG2400' \
--to=gguevel@interfaceconcept.com \
--cc=afleming@freescale.com \
--cc=linuxppc-embedded@ozlabs.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 NNTP newsgroup(s).