Thanks for the quick feedback. This should be fixed in v2. What do you think?
On Tue, Apr 14, 2015 at 5:43 PM, Jens Axboe <[email protected]> wrote: > On 04/14/2015 04:58 PM, Dan Ehrenberg wrote: >> >> In this new mode, sequential trims and writes are interspersed by first >> doing a trim at a particular offset, then doing writes starting from >> that offset until the start of the next trim block, then another trim, >> etc. This workload is designed to match the requirements of NAND flash, >> if trims are implemented as erases. > > > At first I found this a little confusing, but now I get it. It's a bit > different to what other mixed workloads would be. Perhaps rename it to > 'trimwrite'? Also needs adding to the man page and HOWTO. > > -- > Jens Axboe > > -- > To unsubscribe from this list: send the line "unsubscribe fio" in > the body of a message to [email protected] > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
