jthornber
commented
10 years ago Yep, you can use whatever you want. Adding a check that you're using the right version of fio would be helpful.
On 10 October 2014 23:16, Akira Hayakawa notifications@github.com wrote:
Hi, fio tool is changing a lot and I want to use some features in upstream. For example, write_barrier and io_limit which are not available in repo's of Debian 7 I am using.
io_limit is recently fixed and I want to depend on this fix if I can. axboe/fio@ac00233 https://github.com/axboe/fio/commit/ac002339c382d56ffcbf2b15a55d07d9d8c2eac6
Aside this fix, its behavior is subtly different from Debian's fio 2.0.8.
Can I write tests that depend on upstream fio?
Installing fio is a piece of cake. I recommend all users of dmts install the upstream fio because fio is frequently used in dmts, hence the behavior should not be different.
— Reply to this email directly or view it on GitHub https://github.com/jthornber/device-mapper-test-suite/issues/36.
Hi, fio tool is changing a lot and I want to use some features in upstream. For example, write_barrier and io_limit which are not available in repo's of Debian 7 I am using.
io_limit is recently fixed and I want to depend on this fix if I can. https://github.com/axboe/fio/commit/ac002339c382d56ffcbf2b15a55d07d9d8c2eac6
Aside this fix, its behavior is subtly different from Debian's fio 2.0.8.
Can I write tests that depend on upstream fio?
Installing fio is a piece of cake. I recommend all users of dmts install the upstream fio because fio is frequently used in dmts, hence the behavior should not be different.