4. the sequential test might be writing one sector only each time instead of 4096, as it jumps pages in sizes of 4096 ?? (and the size should not be hard-coded) #10

davidsaOpenu · 2016-02-17T23:35:40Z

No description provided.

This commit changes the hard-coded page size to MACROS - responds to issue davidsaOpenu#10

Change-Id: I91d67b80b07337d47389b190249888d4d923c741

davidsaOpenu mentioned this issue Feb 26, 2016

nvme compliance tests crush the system on small disks #15

Closed

ialexyi added a commit to ialexyi/simulator that referenced this issue Jun 7, 2016

Update sector_tests.cc

689f40d

This commit changes the hard-coded page size to MACROS - responds to issue davidsaOpenu#10

davidsaOpenu pushed a commit that referenced this issue Jun 14, 2016

Change the hard-coded page size to MACROS - responds to issue #10

091df5d

Change-Id: I91d67b80b07337d47389b190249888d4d923c741

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

4. the sequential test might be writing one sector only each time instead of 4096, as it jumps pages in sizes of 4096 ?? (and the size should not be hard-coded) #10

4. the sequential test might be writing one sector only each time instead of 4096, as it jumps pages in sizes of 4096 ?? (and the size should not be hard-coded) #10

davidsaOpenu commented Feb 17, 2016

4. the sequential test might be writing one sector only each time instead of 4096, as it jumps pages in sizes of 4096 ?? (and the size should not be hard-coded) #10

4. the sequential test might be writing one sector only each time instead of 4096, as it jumps pages in sizes of 4096 ?? (and the size should not be hard-coded) #10

Comments

davidsaOpenu commented Feb 17, 2016