You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 19, 2024. It is now read-only.
If the purpose of the initialize step is to write data of full capacity sequentially, does it make sure that data is written sequentially when MDTS is smaller than 1M, the block size of initialize step? As I know, if MDTS is smaller than 1M, the device driver, stornvme.sys, divides it to several commands . In this case, does the device driver guarantee the sequential data written? If not, I suggest smaller "DEFAULT_IO_SIZE" such as 128K in precondition.h or add block size parameter in write_num_pass.pm line 78 as "$cmd .= "-b128k " to use smaller block size.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If the purpose of the initialize step is to write data of full capacity sequentially, does it make sure that data is written sequentially when MDTS is smaller than 1M, the block size of initialize step? As I know, if MDTS is smaller than 1M, the device driver, stornvme.sys, divides it to several commands . In this case, does the device driver guarantee the sequential data written? If not, I suggest smaller "DEFAULT_IO_SIZE" such as 128K in precondition.h or add block size parameter in write_num_pass.pm line 78 as "$cmd .= "-b128k " to use smaller block size.
The text was updated successfully, but these errors were encountered: