IETF Logo Mail Archive

Re: [quicwg/base-drafts] QUIC Transport: Flow Control (#3722)

ianswett <notifications@github.com> Mon, 08 June 2020 21:19 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FEE73A041D for <quic-issues@ietfa.amsl.com>; Mon, 8 Jun 2020 14:19:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y7_ISiDsryE3 for <quic-issues@ietfa.amsl.com>; Mon, 8 Jun 2020 14:19:12 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A69803A03FF for <quic-issues@ietf.org>; Mon, 8 Jun 2020 14:19:12 -0700 (PDT)
Received: from github-lowworker-b19c547.va3-iad.github.net (github-lowworker-b19c547.va3-iad.github.net [10.48.17.66]) by smtp.github.com (Postfix) with ESMTP id B75672C1450 for <quic-issues@ietf.org>; Mon, 8 Jun 2020 14:19:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1591651151; bh=MvXUqW1uogjTuvzks4J4Rtta0qW3fy/6l/ImyfZ875w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TyDExxmyvZQpSZAGt+DrDndj+XkXyWDv3WJ2xhcWCysGDHsbkenyhnOtlY3bq9Hp8 drx1iNUcNUyq5gbbQZAHDd74ewMi5NrJ4BxOuPoXze736IMU+MtF/D+WzDoQ9rBJ4u I9zEL1x8iOTz5QVjNHdYXz1uwMVTRqNCT2WhI6Us=
Date: Mon, 08 Jun 2020 14:19:11 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY2TD273AHR7CLWOFV45KGE7EVBNHHCLGB6ZU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3722/640892294@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3722@github.com>
References: <quicwg/base-drafts/issues/3722@github.com>
Subject: Re: [quicwg/base-drafts] QUIC Transport: Flow Control (#3722)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5edeab4fa8593_3a203fe2a1ccd96898144"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/FYv0luimSYpfZy_m2zVL29zorys>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jun 2020 21:19:15 -0000

@evolodina Can you clarify what conditions you're testing, as there are are a lot of variables in flow control.

We send flow control updates much less frequently than anytime there's free credit and a packet is already being sent, and very rarely see flow control blockage, despite doing dynamic window tuning on the server side.  So I'd expect if we did more proactive updates with better bundling, it'd only help.

Bundling flow control updates with ACK frames makes a large amount of sense, because ACK frames free up congestion window space and window updates free up flow control.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3722#issuecomment-640892294

v2.14.0 | Report a Bug | By Email