Re: [tsvwg] UDP Options: on forcing the use of UDP CS=0 in connection with FRAG+LITE

Joe Touch <touch@strayalpha.com> Tue, 02 July 2019 02:17 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C205A12018B for <tsvwg@ietfa.amsl.com>; Mon, 1 Jul 2019 19:17:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level:
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 F2HUcAU6HNzF for <tsvwg@ietfa.amsl.com>; Mon, 1 Jul 2019 19:17:19 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEA071200D7 for <tsvwg@ietf.org>; Mon, 1 Jul 2019 19:17:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=3dpuKllauSWknh3j4rVRdKnKlyB2DKLsjO/rONVjwj8=; b=llm06uyrrt++ba/JcqESzNI4U GrTK4ebxAc8lfEzdqg/Dh2fCFfr3XLm45iR6//4q210Socw685AseH52J6U39LFWEG3RlmWQjtcxe 93TVztOjetbiPd31GTilOaCrEzX0F91vJdGFpR4DG2ZrSVwARxwJROijqUony0NiKjerKOQbje4Zc nkMjVP6X+oOgs/hcG0BQ7bOkV05421/Jn5y215bc/PJ3RC9lHjMg7NjYWAeKX4zDbJMhKMhC2b1m8 y21+eWSHrrWnNJ3GijWyEtVwFWqVrhUUs7E+LrE1aZRsQrO/Da/ZjG/PZOJXacv5lH8F2V468/yrj E3eipGv7Q==;
Received: from cpe-172-250-240-132.socal.res.rr.com ([172.250.240.132]:50832 helo=[192.168.1.77]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1hi8Lu-000KWh-Kw; Mon, 01 Jul 2019 22:17:16 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <C4FD7B8E-E05A-48EA-8F3A-8D91473172FB@strayalpha.com>
Date: Mon, 01 Jul 2019 19:16:59 -0700
Cc: TSVWG <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FAD91A41-CBA0-404B-AE84-DCF43EF86D81@strayalpha.com>
References: <CACL_3VHGtMz3htgfFLRGhjXm=qC7kOXQs+cchtamhh-giBnpLA@mail.gmail.com> <CALx6S35T9ApzMaoSVgHSJPpcpfXsbHHogoBbEjMPj6vH-kxYeA@mail.gmail.com> <CACL_3VE6kr33Vk5si5AxSZNmhqysZZGoy6HK37COUgwbvcRkdA@mail.gmail.com> <24692A9B-4AF1-4E32-A760-7D4908A61262@strayalpha.com> <CACL_3VExhAdFCu-kFLLO5DeRYUOFyJztUgJg-vQmnPoecvzeJg@mail.gmail.com> <6DB954BC-8D40-4347-A172-C00FED1AE4AF@strayalpha.com> <CACL_3VF38oR7emB0K6yrL7Npj4eb-Q-KFVu3=7L66syGaTrJtA@mail.gmail.com> <3E9DF9F3-EEBF-4C74-9633-A8E4ED1B5C01@strayalpha.com> <2977F9B1-73F3-4718-B65D-074EFED848AF@strayalpha.com> <CACL_3VHnVkSNXZoNzYBXX4jSGQuv1NL9UMf=j9YTXLmVb4Oq8Q@mail.gmail.com> <2720454F-8C4E-4C34-B326-C208ECD348A4@strayalpha.com> <CACL_3VF4XiRyS7Nc=eSE-ec+qGo6Xkc3syE+iGXxXPPN=eOpWw@mail.gmail.com> <C4FD7B8E-E05A-48EA-8F3A-8D91473172FB@strayalpha.com>
To: "C. M. Heard" <heard@pobox.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/4TYAdUKlarl9gIAqM9KmWw_aB40>
Subject: Re: [tsvwg] UDP Options: on forcing the use of UDP CS=0 in connection with FRAG+LITE
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jul 2019 02:17:21 -0000

Oh, I should mention why this was an assumption - it allows RDMA-style direct data placement and zero-copy reassembly in the fast-path (happy order) case.

That’s not possible without copies otherwise.

Further, in the most typical expected case of two fragments, it enables zero-copy for the first fragment, which could more than halve the copies even if later fragments are put in holding areas.

Joe

> On Jul 1, 2019, at 6:55 PM, Joe Touch <touch@strayalpha.com> wrote:
> 
> 
> 
>> On Jul 1, 2019, at 5:42 PM, C. M. Heard <heard@pobox.com> wrote:
>> 
>> The original complaint was:
>> 
>>> The solution below doesn't appear to avoid copying/moving large amounts
>>> of data.
>>> 
>>> At a minimum, can you address #2? If we can do this without moving
>>> around a lot of data, it might be viable.
>> 
>> I believe I've addressed that point.
> 
> The assumption was ‘to place the fragments in order using existing efficiencies,’ which assumed the data starts at the beginning of the conventional UDP area in each fragment. That’s what LITE+FRAG does.. You need to copy to achieve that.
> 
> Joe
> 
> 
>