Hi Sanjay,
> I suppose it would still function correctly via the handler, but horribly
slowly.
How important is best performance for the unaligned copy to/from
uncacheable memory?
The challenge of the CELL chip is that X-form of the shift instructions are
microcoded.
The shifts are needed to implement a copy that reads and writes always
aligned.
There is of course the option to not use the X-form of the shift but to
write several copy routines
using immediate shift instructions and to pick the matching copy routine.
This option would of course highly increase the code size of the memcopy
routine.
Kind regards
Gunnar
Sanjay Patel
<[EMAIL PROTECTED]
.com> To
Arnd Bergmann <[EMAIL PROTECTED]>,
19/06/2008 18:13 Gunnar von
Boehn/Germany/Contr/[EMAIL PROTECTED]
cc
Please respond to Mark Nelson <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] linuxppc-dev@ozlabs.org, Michael
com Ellerman <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject
Re: [RFC 1/3] powerpc:
__copy_tofrom_user tweaked for Cell
--- On Thu, 6/19/08, Gunnar von Boehn <[EMAIL PROTECTED]> wrote:
> You are right the main copy2user requires that the SRC is
> cacheable.
> IMHO because of the exception on load, the routine should
> fallback to the
> byte copy loop.
>
> Arnd, could you verify that it works on localstore?
Since the main loops use 'dcbz', the destination must also be cacheable.
IIRC, if the destination is write-through or cache-inhibited, the 'dcbz'
will cause an alignment exception. I suppose it would still function
correctly via the handler, but horribly slowly.
--Sanjay
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
