From: Chris Friesen <chris.friesen@genband•com>
To: Scott Wood <scottwood@freescale•com>
Cc: linuxppc-dev@ozlabs•org, paulus@samba•org, timur@freescale•com
Subject: Re: linux support for freescale e5500 core?
Date: Thu, 16 Sep 2010 15:44:37 -0600 [thread overview]
Message-ID: <4C928FC5.9050700@genband.com> (raw)
In-Reply-To: <20100916163911.6255d359@schlenkerla.am.freescale.net>
On 09/16/2010 03:39 PM, Scott Wood wrote:
> On Thu, 16 Sep 2010 14:06:37 -0600
> Chris Friesen <chris.friesen@genband•com> wrote:
>
>> We're looking at maybe doing some work with an e5500-based system. Is
>> there any support existing/planned for this core?
>
> Check with whoever you'd be getting the hardware from about a BSP.
>
> And yes, it should be supported upstream at some point.
We haven't settled on a vendor yet, so I was just wondering in general
what the story was around support.
>> Also, do we know what the cache line size is--we have some legacy apps
>> that assume 32-byte.
>
> The cache line is 64 bytes. As with e500mc, there is a "dcbz32" mode
> for compatibility, though you probably lose much of the performance
> benefit of dcbz, and it might upset other software that properly checks
> for the cache line size but doesn't use dcbzl.
Right. We currently use a 970-series cpu and have implemented a
per-process flag to indicate whether 32-byte mode is needed or not.
We'd have to do something similar with the new cpu.
One last question--can you comment on the speed of an e5500 relative to
a 970 for integer operations?
Thanks,
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband•com
www.genband.com
next prev parent reply other threads:[~2010-09-16 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 20:06 linux support for freescale e5500 core? Chris Friesen
2010-09-16 21:39 ` Scott Wood
2010-09-16 21:44 ` Chris Friesen [this message]
2010-09-16 22:03 ` Benjamin Herrenschmidt
2010-09-16 22:26 ` Chris Friesen
2010-09-17 0:03 ` Benjamin Herrenschmidt
2010-09-17 5:17 ` Kumar Gala
2010-09-17 5:33 ` Benjamin Herrenschmidt
2010-09-17 6:36 ` Chris Friesen
2010-09-17 7:39 ` Kumar Gala
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=4C928FC5.9050700@genband.com \
--to=chris.friesen@genband$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
--cc=scottwood@freescale$(echo .)com \
--cc=timur@freescale$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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