From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by passt.top (Postfix) with ESMTP id 884585A0082 for ; Tue, 14 Feb 2023 15:22:44 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1676384563; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=b+ky3m6UrcXk3MjioMlRFQXa04ndRWxz9Yze+6ul5+g=; b=g25gC5PblDUFyFy6WpYuNr8hEQKAdCfv1UbrVIheS1gN5qetefovqGch03ZVN2OWimZGin UsmW88o73vou3irNjQM6614WWHGxxcL1nQuWkb81IXmAPqOvMeNtmKSQSWkYC49E9X5Hpm roZFjZh7/wuoGKO1098KDpI2AdbnYiw= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-370-67G-7dFXPn27743zbqzzrA-1; Tue, 14 Feb 2023 09:22:40 -0500 X-MC-Unique: 67G-7dFXPn27743zbqzzrA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 20799857F41; Tue, 14 Feb 2023 14:22:40 +0000 (UTC) Received: from maya.cloud.tilaa.com (unknown [10.33.32.3]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 002741415108; Tue, 14 Feb 2023 14:22:39 +0000 (UTC) Date: Tue, 14 Feb 2023 15:22:31 +0100 From: Stefano Brivio To: David Gibson Subject: Re: Problem with IPv4 performance tests Message-ID: <20230214152231.3f266ea6@elisabeth> In-Reply-To: References: Organization: Red Hat MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Message-ID-Hash: NP5PK3O7DGJZQNWHENBVLFCL6X5KHUAR X-Message-ID-Hash: NP5PK3O7DGJZQNWHENBVLFCL6X5KHUAR X-MailFrom: sbrivio@redhat.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: passt-dev@passt.top X-Mailman-Version: 3.3.3 Precedence: list List-Id: Development discussion and patches for passt Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue, 14 Feb 2023 12:59:02 +1100 David Gibson wrote: > Hi, >=20 > I've been running the tests for the first time since getting back from > holiday. I seem to be getting a consistent failure on the first batch > of IPv4 throughput tests, although the IPv6 tests before it worked fine: >=20 > =3D=3D=3D perf/passt_tcp > > passt: throughput and latency =20 > Throughput in Gbps, latency in =C2=B5s, one thread at 4.8 GHz, 8 streams > = MTU: | 256B | 576B | 1280B | 1500B | 9000B | 65520B | > = |--------|--------|--------|--------|--------|--------| > TCP throughput over IPv6: guest to host = | - | - | 6.5 | 7.6 | 20.7 | 28.1 | > TCP RR latency over IPv6: guest to host = | - | - | - | - | - | 74 | > TCP CRR latency over IPv6: guest to host = | - | - | - | - | - | 227 | > = |--------|--------|--------|--------|--------|--------| > TCP throughput over IPv4: guest to host = | 0 | 0 | 0 | 0 | 0 | 0 | > TCP RR latency over IPv4: guest to host = | - | - | - | - | - | >=20 > I haven't seen a failure like this before, has anyone else seen > something like this? Whoa. I haven't, not even occasionally. > I'm not getting any messages from the iperf client at all - like it > has no connectivity whatsoever, but the non-perf tests are all > passing. The only obvious difference I see are port numbers: that would be port 10003 for functionality tests, and 10002 for throughput tests. Maybe you have something else already bound to it...? Or could it be due to the "new" virtio-net TX hang, fixed by kernel commit d71ebe8114b4 ("virtio-net: correctly enable callback during start_xmit")? The 256-byte MTU test is the one most likely to trigger that condition... --=20 Stefano