• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 6 replies
  • Subscribers 136 subscribers
  • Views 9094 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-760 MP2 gpu memory usage per process

shizhy

Hi, expert,

I am using the phone of MEILAN, which use soc of MT6752 with mali-760 mp2, I want to track process gpu memory usage and found there is a debug node "/d/mali/gpu_memory" which record each process context gpu memory usage.  I found that the data is smaller as expected. So I wrote an test apk which allocates an 4M texture(1024*1024 RGBA) each time I touch the screen, but the gpu memory of the test app increase only 1M each time.  I also tracked the /proc/meminfo, found the free memory decrease about 4M.   so the data of the node "/d/mali/gpu_memory"  are not real gpu memory usage?

  • 0 Arm Employee Badge

    Can you let us know exactly what data the device node is returning - one capture before and after a single allocation would be great - as well as the driver version string?

    If you have an APK reproducer you can share that will help accelerate investigation our side.

    Thanks,
    Pete

  • 0 in reply to Peter Harris

    before:

    mali0                  38215

      kctx-0xe4a90000      12041

      kctx-0xe4b70000        591

      kctx-0xe53f3000      5921

      kctx-0xec855000      10025

      kctx-0xebc49000      4826

      kctx-0xe494f000      4811

    after

    mali0                  39258

      kctx-0xe4a90000      13084

      kctx-0xe4b70000        591

      kctx-0xe53f3000      5921

      kctx-0xec855000      10025

      kctx-0xebc49000      4826

      kctx-0xe494f000      4811

    Attachment is the apk, it just create an 1024*1024 RGBA texture each time when you touch the screen. suppose gpu memory will increase about 4M, but above data increase only about 1M.

    by the way, how to check mali driver version string?

  • 0 Arm Employee Badge in reply to shizhy

    The figures are the number of 4KB pages, not the number of KB, so it seems to be correctly showing a 4MB increase.

    I agree it's not clear and I will ask our kernel driver team to add some units to the print out =P

    Cheers,
    Pete

    P.S. The version string is normally part of the version string. Call glGetString with one of the following enums to get more info about the render state:

    GL_VENDOR : Returns the company responsible for this GL implementation. This name does not change from release to release.
    GL_RENDERER : Returns the name of the renderer. This name is typically specific to a particular configuration of a hardware platform. It does not change from release to release.
    GL_VERSION : Returns a version or release number of the form OpenGL<space>ES<space><version number><space><vendor-specific information>.
  • 0 in reply to Peter Harris

    thanks for your quick reply.

  • 0 in reply to Peter Harris

    Hi Peter,

    my device correctly reports the unit as "pages", so I don't think we need to add units next to the figures, since they are already in the column headings:

                    context name    context addr    used pages  shrink pages  pmem pages  tmem pages      others
=============================================================================================================
  (              Thread-182), kctx-0xeee68000            116          29          2        105          9
  (          surfaceflinger), kctx-0xee058000            571        421          52        394        125
........

    I am glad this was solved, thanks.

  • +1 Arm Employee Badge in reply to Lorenzo Dal Col

    lorenzodalcol Thanks for confirming - looks like the driver team have already improved the report layout in the latest r5px driver release series.

    Pete