On 14/11/2023 17.58, Michael Tokarev wrote:
Fixes: 17257b90be4f "tests: Add migration dirty-limit capability test" Cc: Hyman Huang <yong.hu...@smartx.com> Cc: Juan Quintela <quint...@redhat.com> Signed-off-by: Michael Tokarev <m...@tls.msk.ru> --- tests/qtest/migration-test.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)diff --git a/tests/qtest/migration-test.c b/tests/qtest/migration-test.c index 5752412b64..0fbaa6a90f 100644 --- a/tests/qtest/migration-test.c +++ b/tests/qtest/migration-test.c @@ -3138,7 +3138,7 @@ static void test_migrate_dirty_limit(void) uint64_t throttle_us_per_full; /* * We want the test to be stable and as fast as possible. - * E.g., with 1Gb/s bandwith migration may pass without dirty limit, + * E.g., with 1Gb/s bandwidth migration may pass without dirty limit, * so we need to decrease a bandwidth. */ const int64_t dirtylimit_period = 1000, dirtylimit_value = 50;
Reviewed-by: Thomas Huth <th...@redhat.com>
