On 9/1/20 2:19 AM, Shin'ichiro Kawasaki wrote: > The max_open_zones and job_max_open_zones option control number of write target > open zones within the specified limit. Currently, this write target zone > accounting is not accurate enough. Even with these options set, the limits can > exceed during write workloads. > > This patch series improves accuracy of the open zones accounting. The first > patch moves the moment to decrement number of currently open zones from write > command submit to write command completion. This avoids zone writes beyond the > limit caused by concurrent write commands at queue depths approaching the max > limits. The second and third patches fix the open zone status initialization > issue. Other following patches improve t/zbd scripts to take maximum write > target zone limit and allow to test devices with the limit. Applied, thanks. -- Jens Axboe
