Message ID | 20221102025702.1664101-1-yi.zhang@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | fix and improvement for xfs log size change from new xfsprogs version | expand |
On 11/1/22 19:56, Yi Zhang wrote: > Hi > > The first patch addressed nvme/012 nvme/013 failure which introduced > from xfsprogs v5.19.0, the minimun xfs log size change to 64m > > The second patch introduced one new function _require_test_dev_size_mb > > The third patch add one new parameter to _run_fio_verify_io, this will > allow fio I/O size definition to the test case > > > V2: > Update the new function to _require_test_dev_size_mb and nvme/035 > to call it for test dev size checking for the second patch > Update the title and description for better reflect the change for the > third patch > > V1: https://lore.kernel.org/linux-block/20221024061319.1133470-1-yi.zhang@redhat.com/ overall this looks good to me, I believe you have tested this to confirm the stability of the new size for the testcases, Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com> -ck
On Nov 02, 2022 / 10:56, Yi Zhang wrote: > Hi > > The first patch addressed nvme/012 nvme/013 failure which introduced > from xfsprogs v5.19.0, the minimun xfs log size change to 64m > > The second patch introduced one new function _require_test_dev_size_mb > > The third patch add one new parameter to _run_fio_verify_io, this will > allow fio I/O size definition to the test case Have applied the patches. Please note that I took a liberty to do minor edits in the second patch. Thanks!