• State Accepted Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 137 subscribers
  • Views 8255 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Mali-T880 in Helio X20

david

Hello, I am developing software based on mali-T880 (X20) with OpenCL.I was wondering the specific structure of the mali-T880, including the number of shadercores,the structure of each shadercore ,the size of the L1 cache and the size of L2 cache, which is helpful to improve the efficiency of the algorithm.

thanks a lot.

Parents
  • 0 Arm Employee Badge in reply to david
    Hi David,

    > I was wondering that my algorithm is only used the arithmetic pipeline or it is also used the texture pipeline.

    I do not know what your algorithm is, so cannot give you a definitive answer, but in general the read-only filtered texture access built-in functions will use the texture pipe and all other memory access (e.g. pointer based data load/store, imageLoad/imageStore built in functions) will use the load/store unit. The two caches are independent, so if you are not using the texturing unit you will only have 16KB of L1 cache per core available.

    One important thing to note with Mali for compute is that there is no physically distinct backing for OpenCL "local memory"; both local and global memory pools are simply backed by cached system memory. Do not copy data resources from global to local pools in the belief it helps performance; it will make things worse on Mali due to increased pressure on the L1 LS cache.

    HTH,
    Pete
Reply
  • 0 Arm Employee Badge in reply to david
    Hi David,

    > I was wondering that my algorithm is only used the arithmetic pipeline or it is also used the texture pipeline.

    I do not know what your algorithm is, so cannot give you a definitive answer, but in general the read-only filtered texture access built-in functions will use the texture pipe and all other memory access (e.g. pointer based data load/store, imageLoad/imageStore built in functions) will use the load/store unit. The two caches are independent, so if you are not using the texturing unit you will only have 16KB of L1 cache per core available.

    One important thing to note with Mali for compute is that there is no physically distinct backing for OpenCL "local memory"; both local and global memory pools are simply backed by cached system memory. Do not copy data resources from global to local pools in the belief it helps performance; it will make things worse on Mali due to increased pressure on the L1 LS cache.

    HTH,
    Pete
Children