Re: Proposal to replace ACK block count with ACK length

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Mon, 11 June 2018 15:43 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 4F51D130E39 for <quic@ietfa.amsl.com>; Mon, 11 Jun 2018 08:43:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] 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 RZ_19icsZpAF for <quic@ietfa.amsl.com>; Mon, 11 Jun 2018 08:43:22 -0700 (PDT)
Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::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 78793130E31 for <quic@ietf.org>; Mon, 11 Jun 2018 08:43:22 -0700 (PDT)
Received: by mail-qt0-x233.google.com with SMTP id o9-v6so20672057qtp.3 for <quic@ietf.org>; Mon, 11 Jun 2018 08:43:22 -0700 (PDT)
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=D/5UzF84eL+kJZTXKWOywLsCa/qxokA1jLW8wf+cnHM=; b=mUIn+ndhLd6xDB8H5MZx49vaGhnt9VdQdwUh7my0C+nEhjtJ1mO31COM5JxTYSoZtZ oU1Aic1jDcogRPTImGCn6qyy48ar15QIPT2jfWxpvY2hJCSsSdjJ3uRsJbTEa5c78ALY OXo0FtzRadafDDa8mBNo02qxs0hj0HF9g1ddA6TFHoCNKh9bYx2Vid6j5W9DIM2TC8Xt BPB5dBEegjpsG/PJYuPTWr3+QTxD7DVjjuSN8LXilgqbXL4C+LCFOWyF1+jQGke+3sFh s+riDwuIiQVt2ylZT37i5JvUJqZ3KHHDmvrMLN/Sbu9VkLbnOBbVuTE/5pladuYuh1WM NKfg==
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=D/5UzF84eL+kJZTXKWOywLsCa/qxokA1jLW8wf+cnHM=; b=Id2J3/+zh63ClHKo6qh13zqF3SGcN3c5vkcdC5B7wogLllClQuMM2nn9gF6fsxEOwg QOoK4aeaubKvp5+ohgdVrHrWsnHqaKGIcULeRt77bIIVNnxVsH+9f/3nrTlJQznt2z5D hAa/0gUK1sVwgc9a8CE3BfpdbBqYg556n/u446g7H+1ptGgVSfkkzuziW72yc36NSBqR 7yrammnbADvCBRh7oMhPg5M8lhzC+80LnyNGTS1BdSHS3NcqTo/Qy8g3G0qxC0js0cu2 0bMh6Gkcjg8R1nQD6LrWohFc3XenkViuELNnbupSCfPiBH3KBQ8mOg67wrS7uMXMtAP/ opEQ==
X-Gm-Message-State: APt69E2w/c/xW/gdI7EtzGnni3n1bHIy3eR2C0XGp+NfUv607m//NwA5 MyQbAWKlgfZM9zh+8JJKtpYaVg==
X-Google-Smtp-Source: ADUXVKJHcbOvEOTm2lNHXN1S30/tnydiKiKPbkaMli+t3iGf5cfCWgwSHV6wumu6FuY76yacDuHYgQ==
X-Received: by 2002:aed:3d09:: with SMTP id g9-v6mr16746275qtf.272.1528731801593; Mon, 11 Jun 2018 08:43:21 -0700 (PDT)
Received: from ubuntu-dmitri (ool-45715890.dyn.optonline.net. [69.113.88.144]) by smtp.gmail.com with ESMTPSA id k67-v6sm4811392qte.95.2018.06.11.08.43.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Jun 2018 08:43:21 -0700 (PDT)
Date: Mon, 11 Jun 2018 11:43:15 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: "Deval, Manasi" <manasi.deval@intel.com>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Proposal to replace ACK block count with ACK length
Message-ID: <20180611154244.GA27622@ubuntu-dmitri>
Mail-Followup-To: "Deval, Manasi" <manasi.deval@intel.com>, IETF QUIC WG <quic@ietf.org>
References: <1F436ED13A22A246A59CA374CBC543998B832414@ORSMSX111.amr.corp.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1F436ED13A22A246A59CA374CBC543998B832414@ORSMSX111.amr.corp.intel.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/KiFmLwF39byPHqqR8Xn-rvfP_GM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.26
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: Mon, 11 Jun 2018 15:43:25 -0000

On Mon, Jun 11, 2018 at 03:33:35PM +0000, Deval, Manasi wrote:
> -        Moving the ACK length to the front of the ACK allows the
>          flexibility of either reading the entire ACK or reading the
>          first 16 bits and skipping over the length. This is a useful
>          feature for the case where ACK processing is split into
>          multiple layers. Depending on the processor this is run on,
>          there are different advantages -

Just a note.  In my experience, the cost of parsing an ACK frame is
negligible compared to the cost of processing an ACK frame: that is,
poking at various memory locations to discard newly ACKed packets.

  - Dmitri.