IETF Logo Mail Archive

Re: Deadlocking in the transport

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Wed, 10 January 2018 20:06 UTC

Return-Path: <dtikhonov@litespeedtech.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 669ED12711B for <quic@ietfa.amsl.com>; Wed, 10 Jan 2018 12:06:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 mM_iOraFaYkw for <quic@ietfa.amsl.com>; Wed, 10 Jan 2018 12:06:50 -0800 (PST)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 BB51E126DED for <quic@ietf.org>; Wed, 10 Jan 2018 12:06:49 -0800 (PST)
Received: by mail-qk0-x233.google.com with SMTP id j185so567466qkc.5 for <quic@ietf.org>; Wed, 10 Jan 2018 12:06:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=rALQYFvAOJAzJuSvN6JCR+3ObsgFJDr4l6JTr/58QSg=; b=Ke/zVu8SvKzbjTfQ3LP2iuZK9EuwgMAXNI3yeC6bXYLut33LbyZIDhvqBL2afU93La 2A/zWdBiyFM6oG1n4BZDhgQm6BTtmUTQFWdCRIfSUD3InpH9Sr8Fq0nb+DPBQg/bI+Bt JHDJqtizZ4vlDSCNUuFYKit+xuZgt6uJ1X+RdsAgozD2Ano9e4/qdVZbdVORVzEJ3M+E AGo4qaEsqUt/LV7cgdo9X6/gHexfPgzof9hviONG+LNTW43rX9PaDGj6j8a+GA0mErjK aV8aLrDcSEKCeb05fgtISqAwS8uBPB+JmdaRwq8D1ayjtbEJGb7HpM3qXxGYlKP67w0A XTFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=rALQYFvAOJAzJuSvN6JCR+3ObsgFJDr4l6JTr/58QSg=; b=QViOwx1+pUGcy9doCwaYmSHdBWQjoF2LsAbWSKZrPGVWqbF4+LbHoq79fdnnbFlOz7 oXrCDIzfBIXQpvyWN2fIRdMjBoHkPRSIyGsbfxRhiBq6zI4R30hThemSfkBl3XFcUctg erwQ7xKztC88Uj2ligwD0RDTLN1pJVXg0WFRjx/zDBgbt26lp/NOCyGTMYlR6kDrM7a8 jVM5M+Rs4iKNlALpqZmwUQpiAK7AC1HHYFV9TptGTSJPwx7DGQqcTwn9swX+J2IwyxOc zlfWFL2gDhQb8Of+AFv/U74Is169Ji5OW6vX8xmPxdB6lhWdz4+nq6QGp7caQNOmTpaT Yjtw==
X-Gm-Message-State: AKwxytdxJAjSnn7aNVHuQmKWDfwWexuRYD7uBx+xYbgpuUMKe4H2iorU Aqe+YALcPZuB2FAXeC/TNZPijg==
X-Google-Smtp-Source: ACJfBousY+GDlsGLiVBbE6lN4I6vp2sJE7gCgHRKnyCMA32bMfmmMqC7bV//c3tn0DomS/ANWuZ2FA==
X-Received: by 10.55.53.205 with SMTP id c196mr16849894qka.311.1515614808885; Wed, 10 Jan 2018 12:06:48 -0800 (PST)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id s41sm1767429qtk.39.2018.01.10.12.06.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Jan 2018 12:06:48 -0800 (PST)
Date: Wed, 10 Jan 2018 15:06:46 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Jana Iyengar <jri@google.com>
Cc: Charles 'Buck' Krasic <ckrasic@google.com>, QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>
Subject: Re: Deadlocking in the transport
Message-ID: <20180110200646.GB30573@ubuntu-dmitri>
Mail-Followup-To: Jana Iyengar <jri@google.com>, Charles 'Buck' Krasic <ckrasic@google.com>, QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>
References: <CABkgnnUSMYRvYNUwzuJk4TQ28qb-sEHmgXhxpjKOBON43_rWCg@mail.gmail.com> <CAGD1bZYV7iHg_YarUMqUSnpbAB2q8dwEWO=dHE2wbw8Oea_zfA@mail.gmail.com> <CAD-iZUY-Y-MO_T74JmP6B9XVj=91eVovfcWnE=9s9kd0Ji+CnA@mail.gmail.com> <CAGD1bZa7ugOTT11qOKfCm4NFdi+t-pdrXnscWHgg0bO5tgUqmg@mail.gmail.com> <20180110194716.GA30573@ubuntu-dmitri> <CAGD1bZYiDOakLYNppMBr=99JreX3Xr2zkS7O2DRNfvr_o0NUbg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAGD1bZYiDOakLYNppMBr=99JreX3Xr2zkS7O2DRNfvr_o0NUbg@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/DJc0K3GfI8yUecgIFVm0e4vHJc8>
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 20:06:52 -0000

On Wed, Jan 10, 2018 at 12:04:11PM -0800, Jana Iyengar wrote:
> On Wed, Jan 10, 2018 at 11:47 AM, Dmitri Tikhonov <
> dtikhonov@litespeedtech.com> wrote:
> 
> > On Wed, Jan 10, 2018 at 11:34:11AM -0800, Jana Iyengar wrote:
> > > I agree. That's what I meant by priorities solving it -- that the shared
> > > resource (connection-level flow buffer), if consumed in priority order at
> > > the sender, avoids this deadlock. This  assumes that the application can
> > > express this to the transport of course.
> >
> > Even if the application can express it, the transport is not guaranteed
> > to consume the data in priority order: see the specification [1].
> 
> I don't see the text in that section that says otherwise. Under what
> conditions does the transport invert application stream priorities?

This is the text:

  " When deciding which streams to dedicate resources to, QUIC
  " SHOULD use the information provided by the application.
    ^^^^^^

  - Dmitri.

v2.23.0 | Report a Bug | By Email