• Locked Locked
  • Replies 8 replies
  • Subscribers 119 subscribers
  • Views 3800 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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 7th October 2010 at http://forums.arm.com

    If you're only writing to the output (not reading and writing) then I'm not sure there's much you can do besides
      - write the output in at least 32-bit chunks (maybe even larger, e.g. STM) -- writing bytes will stall the write buffer sooner
      - make sure you're only writing the output once
      - write the output in consecutive ascending addresses (actually, that probably only helps if the output is already in the cache, which I'm guessing is not happening here)
      - try to find out if the memory timing is set as fast as possible in whatever memory controller you're using
Reply
  • Arm Employee Badge
    Note: This was originally posted on 7th October 2010 at http://forums.arm.com

    If you're only writing to the output (not reading and writing) then I'm not sure there's much you can do besides
      - write the output in at least 32-bit chunks (maybe even larger, e.g. STM) -- writing bytes will stall the write buffer sooner
      - make sure you're only writing the output once
      - write the output in consecutive ascending addresses (actually, that probably only helps if the output is already in the cache, which I'm guessing is not happening here)
      - try to find out if the memory timing is set as fast as possible in whatever memory controller you're using
Children
No data