IETF Logo Mail Archive

Re: Deadlocking in the transport

Martin Thomson <martin.thomson@gmail.com> Wed, 10 January 2018 21:54 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82F7412E042 for <quic@ietfa.amsl.com>; Wed, 10 Jan 2018 13:54:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 qkZEZwLwcUTq for <quic@ietfa.amsl.com>; Wed, 10 Jan 2018 13:54:05 -0800 (PST)
Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6955120725 for <quic@ietf.org>; Wed, 10 Jan 2018 13:54:04 -0800 (PST)
Received: by mail-ot0-x230.google.com with SMTP id 5so428549oth.8 for <quic@ietf.org>; Wed, 10 Jan 2018 13:54:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=t7wwWHi9yRsqST8dEzAIUplbEGyrJPtuqQnqgr8/ELw=; b=OsFz0g8kB5bsV5wwlsraFd5Yp+n83wkaaathGWlf4PR5gw5TW6ICtsLnN1xsiIA8Su l1GjgFPYMKulmurn4mkQNDVbijh80OAhf8Q6/dQCPazqlHlXg7XrIRvRAbHd2IC5Pn9o RMQQt7rwModM2JkOQrMlsSrSgznLCE00N+LufKHn1WnjBnyJaf98umTeo0XZ6rGhJlEq 8Wxo+LvYHe0+y+rMS3xNfbkaVpkziBoyVawhQQ8Pm4ayI8J/OnO9hcIqhBC/MrYZ2XDR +vR5y8lOUMSW1a4YQbk/4gFSDyB/uKuaLwcjPaugmlGRyNOg7he6B7lZq1iBndga9gYv ZU2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=t7wwWHi9yRsqST8dEzAIUplbEGyrJPtuqQnqgr8/ELw=; b=dMMaQQ8PU3qkh5GPbahbTh0cKtmtEKxDq4L7xwXkFa7/UVhOqYnyd2/I1V1RcWAq25 fc+JV/oTRJg4nUCDkQXfn9GXZXthqNP3oOOGwg7+2t1K8WjE47muS2bCDgfvKl3UbeO+ 4AdrXia9hH7pjMo6KHdNdc7UjZFkrfdL8MKB06I838ye5GEw1a/Q1j2SdZ/4DL8SKwny zUldsFZRMRHFXKRKii6vXRt5t0/mA+K40ceNXdTXBSWMj8BqHhbd3cUoOft15MBoyskn pyXrGuB/KKpd+UUyJfYwZNqk5AtjDADsrBZvJmPI9z0QEEJZHt/fqdvQtZFXehE2ikdm Ctzg==
X-Gm-Message-State: AKwxytf6QPJirfGiaIkWohdY1YrQwnQFSbXSjDLcPnvp4gC+NE0X7x9U FT/Lpwce96ODdGuAiTui1lf/ixYZnCVWgg90G/wCJw==
X-Google-Smtp-Source: ACJfBov82261uv7Slrb3CsLbfylk4F+szPll8+S+3DT1yQWrNYchXLURZfhOasNo9kOyHFCTlMMjccPZ0Sfwlw3v2B0=
X-Received: by 10.157.68.154 with SMTP id v26mr3748751ote.308.1515621244168; Wed, 10 Jan 2018 13:54:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.39.16 with HTTP; Wed, 10 Jan 2018 13:54:03 -0800 (PST)
In-Reply-To: <65EBA092-9DEF-4C9E-9DB8-AA490CA60598@trammell.ch>
References: <CABkgnnUSMYRvYNUwzuJk4TQ28qb-sEHmgXhxpjKOBON43_rWCg@mail.gmail.com> <65EBA092-9DEF-4C9E-9DB8-AA490CA60598@trammell.ch>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 11 Jan 2018 08:54:03 +1100
Message-ID: <CABkgnnVFHu6UhdUJYLUKXJyz7oGVdqKpaYz=eEhUR5_nNOQeXw@mail.gmail.com>
Subject: Re: Deadlocking in the transport
To: "Brian Trammell (IETF)" <ietf@trammell.ch>
Cc: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/IIkqGciQR1w0n_mNLkCXUJesuOM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 21:54:06 -0000

On Wed, Jan 10, 2018 at 6:04 PM, Brian Trammell (IETF) <ietf@trammell.ch> wrote:
> Do we have any actual numbers on how much efficiency can actually be squeezed out of allowing compression dictionaries to create unbounded dependencies between streams on common, non-pathological workloads?

Dmitri ran some tests with QMIN, which doesn't create dependencies,
and found that for a time compression efficiency degraded noticeably
if it couldn't create dependencies.  I'll let Dmitri speak to that
point.  The shortcoming rectifies itself reasonably quickly, though
Roberto makes the point that this is precisely the point where
compression matters most.  It's a point that the header compression
folks are still debating.

(The dependencies wouldn't be unbounded.  One advantage of the
mechanism that QMIN proposes is that these dependencies are pretty
narrowly constrained and well understood.)

v2.23.0 | Report a Bug | By Email