> The reset_zone flag that is defined in fio_zone_info structure is
> only referenced in zbd_adjust_block() function. Convert this flag
> to a local variable and save some room in zbd_info array which can
> be pretty large when running fio against high capacity zoned devices.
This flag should be kept.
Test can crash or be interrupted leaving hw in indeterminate state,
it must be restarted from clean state. Or test can be precondition and
zone should not be reset.
Can't distinguish these two cases from write pointers alone.
Given that precondition and real workload can be in different fio
instances, this information must be somehow given to fio process
and either force or not force zone reset (config option obviously)
> @@ -41,7 +40,6 @@ struct fio_zone_info {
> enum zbd_zone_type type:2;
> enum zbd_zone_cond cond:4;
> unsigned int open:1;
> - unsigned int reset_zone:1;
Does it save space? Bitfields stick together after all.
