1. 11 6月, 2015 1 次提交
  2. 03 6月, 2015 1 次提交
  3. 09 12月, 2014 2 次提交
  4. 27 8月, 2014 1 次提交
  5. 02 6月, 2014 1 次提交
  6. 18 1月, 2014 1 次提交
  7. 22 7月, 2013 1 次提交
  8. 21 1月, 2013 2 次提交
  9. 29 11月, 2012 1 次提交
    • A
      On crash memory test rewrote so that it actaully works. · cd99c14e
      antirez 提交于
      1) We no longer test location by location, otherwise the CPU write cache
      completely makes our business useless.
      2) We still need a memory test that operates in steps from the first to
      the last location in order to never hit the cache, but that is still
      able to retain the memory content.
      
      This was tested using a Linux box containing a bad memory module with a
      zingle bit error (always zero).
      
      So the final solution does has an error propagation step that is:
      
      1) Invert bits at every location.
      2) Swap adiacent locations.
      3) Swap adiacent locations again.
      4) Invert bits at every location.
      5) Swap adiacent locations.
      6) Swap adiacent locations again.
      
      Before and after these steps, and after step 4, a CRC64 checksum is computed.
      If the three CRC64 checksums don't match, a memory error was detected.
      cd99c14e
  10. 22 11月, 2012 1 次提交
  11. 09 11月, 2012 2 次提交
  12. 27 4月, 2012 1 次提交
  13. 13 4月, 2012 1 次提交
  14. 11 4月, 2012 1 次提交
  15. 19 3月, 2012 4 次提交
  16. 18 3月, 2012 2 次提交