It should be capable to do that. Report your issue if you find out it does not do the job. Capture your fio workload with blktrace, then run captured traces through btrecord with small -m value and finally replay back with btreplay.... Not sure how replay is useful in this case when you do have access to fio to generate the same IO workload for you. On Wed, Apr 22, 2015 at 3:53 PM, Brandon Schwartz <schwartz.xn@xxxxxxxxx> wrote: > And by blkreplay, I meant replay the blktrace with FIO > > On Wed, Apr 22, 2015 at 2:52 PM, Brandon Schwartz <schwartz.xn@xxxxxxxxx> wrote: >> Is there an accurate way to capture idle time with blktrace? For >> example, if I run/trace the following FIO script: >> >> [global] >> direct=1 >> ioengine=libaio >> readwrite=read >> blocksize=512k >> filename=/dev/sdd >> >> [read] >> runtime=10 >> name=read >> >> [read2] >> stonewall=1 >> startdelay=40 >> runtime=10 >> name=read2 >> >> And attempt to replay it using blkreplay, it will ignore the wait time >> and simply read for 20seconds instead of read 10s, wait for 40s, read >> 10s. >> >> Regards, >> Brandon > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrace" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-btrace" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
