Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.

We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.

Thank you for your understanding.

  • State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 8 replies
  • Subscribers 137 subscribers
  • Views 31809 views
  • Users 0 members are here
Options
Related
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

samplerExternalOES performance on Mali-400

reciprocal

Hi,

I've just noticed that texture lookups using samplerExternalOES (as specified in the OES_EGL_image_external extension) seem to come with a performance impact on Mali-400, at least if the instruction counts reported by Mali Offline Compiler are correct.

While a texture2D sampler lookup takes 1 cycle, the Mali Offline compiler reports the following for a samplerExternalOES access:

Number of instruction words emitted:            5
Number of cycles for shortest code path:        2
Number of cycles for longest code path:         5

Could someone shed some light on why accessing a samplerExternalOES would be so expensive?

How can I ensure that the fast path is hit (2 cycles)?

Is there a - perhaps less flexible - alternative to OES_EGL_image_external, which would allow for zero-copy textures without this overhead?

Could the cycle counts just be misreported by the Mali Offline Compiler?

Parents Reply Children
No data