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.129.124]) by passt.top (Postfix) with ESMTP id D9F1E5A026F for ; Fri, 29 Sep 2023 17:44:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1696002264; 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=rNFYoWTb+5gYSNPARHvOlPeZZNIT03JfuDaek01rwLo=; b=XLg/oPeU6Zl3NgxNf28fBA81z7nasSbRv40clYXo0+mzdZulDBmZgwfZ8uVnoad56txxdP BhED3O4oMNSvhsg5/wKU0JXxDdJ9hNX49kB25i4NC0iR0n0937YERdZuxOkTtv4NjJSgWA u6S9e3Dd592UlVVJe0dHrNwnR86WvXo= 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-413-6u0Oums0O_iULwZ0KvrFug-1; Fri, 29 Sep 2023 11:44:21 -0400 X-MC-Unique: 6u0Oums0O_iULwZ0KvrFug-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 104A6811E7E; Fri, 29 Sep 2023 15:44:21 +0000 (UTC) Received: from elisabeth (unknown [10.39.208.38]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D7DCE40C6EBF; Fri, 29 Sep 2023 15:44:19 +0000 (UTC) Date: Fri, 29 Sep 2023 17:44:12 +0200 From: Stefano Brivio To: passt-dev@passt.top, David Gibson Subject: Re: [PATCH v2 2/3] tcp: Force TCP_WINDOW_CLAMP before resetting STALLED flag Message-ID: <20230929174412.52a93c03@elisabeth> In-Reply-To: <20230929150446.2671959-3-sbrivio@redhat.com> References: <20230929150446.2671959-1-sbrivio@redhat.com> <20230929150446.2671959-3-sbrivio@redhat.com> Organization: Red Hat MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-ID-Hash: UBOX6JW6FJKJ4TXQ53H7NG7W35L3USTP X-Message-ID-Hash: UBOX6JW6FJKJ4TXQ53H7NG7W35L3USTP 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: Matej Hrica X-Mailman-Version: 3.3.8 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 Fri, 29 Sep 2023 17:04:45 +0200 Stefano Brivio wrote: > It looks like we need it as workaround for this situation, readily > reproducible at least with a 6.5 Linux kernel, with default rmem_max > and wmem_max values: > > - an iperf3 client on the host sends about 160 KiB, typically > segmented into five frames by passt. We read this data using > MSG_PEEK > > - the iperf3 server on the guest starts receiving > > - meanwhile, the host kernel advertised a zero-sized window to the > receiver, as expected Gosh, sorry, I forgot all the s/receiver/whatever/ here. Fixed locally and not reposting, unless there's something else... -- Stefano