• Locked Locked
  • Replies 8 replies
  • Subscribers 119 subscribers
  • Views 3833 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

[ARM926EJS] improve write miss

stanley shih
Note: This was originally posted on 5th October 2010 at http://forums.arm.com

Hello experts,

    The platform I am using is ARM926EJS. Cache policy is write-back and only read-allocate.
    From the profile result, the program I want to optimize has too many write misses (write buffer refill)
    Can anyone give me some guidelines or tricks to improve my program? thanks.

BR,
Stanley
Parents
  • Arm Employee Badge
    Note: This was originally posted on 5th October 2010 at http://forums.arm.com

    The platform I am using is ARM926EJS. Cache policy is write-back and only read-allocate.
        From the profile result, the program I want to optimize has too many write misses (write buffer refill)
        Can anyone give me some guidelines or tricks to improve my program? thanks.


    You'll get write buffer stalls if the memory you were writing was not actually cacheable, so it might be worth double checking that the memory being written is marked cachable in the MMU tables.

    Otherwise, you may need to improve the spatial locality of your writes (search for "strip mining", "blocking" and/or "tiling").

    How much data are you reading/writing?  How big is your data cache?
Reply
  • Arm Employee Badge
    Note: This was originally posted on 5th October 2010 at http://forums.arm.com

    The platform I am using is ARM926EJS. Cache policy is write-back and only read-allocate.
        From the profile result, the program I want to optimize has too many write misses (write buffer refill)
        Can anyone give me some guidelines or tricks to improve my program? thanks.


    You'll get write buffer stalls if the memory you were writing was not actually cacheable, so it might be worth double checking that the memory being written is marked cachable in the MMU tables.

    Otherwise, you may need to improve the spatial locality of your writes (search for "strip mining", "blocking" and/or "tiling").

    How much data are you reading/writing?  How big is your data cache?
Children
No data