- 27 Oct, 2020 1 commit
-
-
David CARLIER authored
(cherry picked from commit f971a5d8)
-
- 16 Dec, 2015 2 commits
-
-
antirez authored
The old test, designed to do a transformation on the bits that was invertible, in order to avoid touching the original memory content, was not effective as it was redis-server --test-memory. The former often reported OK while the latter was able to spot the error. So the test was substituted with one that may perform better, however the new one must backup the memory tested, so it tests memory in small pieces. This limits the effectiveness because of the CPU caches. However some attempt is made in order to trash the CPU cache between the fill and the check stages, but not for the addressing test unfortunately. We'll see if this test will be able to find errors where the old failed.
-
antirez authored
-
- 09 Dec, 2014 1 commit
-
-
antirez authored
-
- 01 Dec, 2014 1 commit
-
-
Jan-Erik Rediger authored
-
- 08 Aug, 2014 1 commit
-
-
Xian Li authored
Closes #1614
-
- 21 Jan, 2013 1 commit
-
-
antirez authored
This closes issue #859, thanks to @erbenmo.
-
- 29 Nov, 2012 1 commit
-
-
antirez authored
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.
-
- 21 Nov, 2012 1 commit
-
-
antirez authored
-
- 08 Nov, 2012 1 commit
-
-
antirez authored
-
- 27 Apr, 2012 1 commit
-
-
antirez authored
-
- 12 Apr, 2012 1 commit
-
-
antirez authored
-
- 11 Apr, 2012 1 commit
-
-
antirez authored
-
- 19 Mar, 2012 1 commit
-
-
antirez authored
-
- 18 Mar, 2012 3 commits
-
-
antirez authored
More memory tests implemented. Default number of iterations lowered to a more acceptable value of 50.
-
antirez authored
-
antirez authored
Number of iteration of --test-memory is now 300 (several minutes per gigabyte). Memtest86 and Memtester links are also displayed while running the test.
-
- 16 Mar, 2012 2 commits