Re: [tsvwg] RDMA Support by UDP FRAG Option

"C. M. Heard" <heard@pobox.com> Sun, 20 June 2021 23:36 UTC

Return-Path: <heard@pobox.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 8BAB03A16C6 for <tsvwg@ietfa.amsl.com>; Sun, 20 Jun 2021 16:36:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.898
X-Spam-Level:
X-Spam-Status: No, score=-0.898 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.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 WkeTzTAN0aoE for <tsvwg@ietfa.amsl.com>; Sun, 20 Jun 2021 16:36:36 -0700 (PDT)
Received: from pb-smtp2.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB1F63A16C3 for <tsvwg@ietf.org>; Sun, 20 Jun 2021 16:36:36 -0700 (PDT)
Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id B2817D016E for <tsvwg@ietf.org>; Sun, 20 Jun 2021 19:36:30 -0400 (EDT) (envelope-from heard@pobox.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h= mime-version:references:in-reply-to:from:date:message-id:subject :to:cc:content-type; s=sasl; bh=Pqu6eYEb1MfPxWHGxFoPw6Ssc4kRWbGX lWZEVqWDEJw=; b=mCiI18IslYyTFbaEcxztAdU9ZhQwovPm+oziKQv5JXkU5xh4 hAiqPLGUi/dutxG5hpoolwhZOqqQ4ENMdYQWaff1e8BIkqn3lVrhOwj0QVZB6Ntx lG6BMasXf1kX4j+6taWqlHGNfZlZSc84NGZP06OIV0xhomqDfGKXK0Ja96c=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id AACEBD016D for <tsvwg@ietf.org>; Sun, 20 Jun 2021 19:36:30 -0400 (EDT) (envelope-from heard@pobox.com)
Received: from mail-io1-f53.google.com (unknown [209.85.166.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 263C4D016C for <tsvwg@ietf.org>; Sun, 20 Jun 2021 19:36:30 -0400 (EDT) (envelope-from heard@pobox.com)
Received: by mail-io1-f53.google.com with SMTP id o5so11911444iob.4 for <tsvwg@ietf.org>; Sun, 20 Jun 2021 16:36:30 -0700 (PDT)
X-Gm-Message-State: AOAM533bF0RygdT/l5B7gMS9IexWX2EC/v5GoiqRqRbkfaccqzvRPlU3 gB6k/ai+RF/rPbsMfA3hlMEUCBbPoew9JkMkF9I=
X-Google-Smtp-Source: ABdhPJw2ZbkQevkNO/cz3YQNBA7ifQbrhFBbtQ7Ur1b2JzLBj1hh1ZcfjgJ4/w0RYeNSqtIB30PjR+F/ssQR2ixuzPs=
X-Received: by 2002:a5d:9c02:: with SMTP id 2mr17573440ioe.195.1624232189571; Sun, 20 Jun 2021 16:36:29 -0700 (PDT)
MIME-Version: 1.0
References: <CACL_3VEyLdQZ-3hvzXxyA8ehtWs2hXESZ2OqyAx+BeSg85+-cA@mail.gmail.com> <CACL_3VFE4TjKvmkfZjvNpWo6vVfKjz5w85=Q+yqnYZKcwbYLmQ@mail.gmail.com> <63FFC34B-2179-47F1-B325-21CAC3D1543A@strayalpha.com> <CACL_3VHTfxWaBj7TFEmBXBqovrrAj7XuFEZFUag_iBHr3Hx09g@mail.gmail.com> <0EBFC9B0-591A-4860-B327-6E617B83F4D1@strayalpha.com> <CALx6S34pT81TbfQDk2vKF8wBrXL312As79K=rEzUQ3Lmg7UvpA@mail.gmail.com> <7C51D926-9DBB-41F5-93B2-10F716F672B1@strayalpha.com> <CALx6S37uN8TsXQZ3cv5jmxwxSyBRjK=-GQ_MsWxPWSs21XoGHw@mail.gmail.com> <CACL_3VEx7+VnLz7OLdXyhZU41e+-oBz3dc8JdMV_7pLMfic6=w@mail.gmail.com> <fcc8762f-c042-7999-d2e4-f28384950a19@erg.abdn.ac.uk> <CALx6S36sWGcZmFpAhF4DfOMyf6Z0w5F9bemNfeM1yWV-r0M+BA@mail.gmail.com> <8af3abf9-943f-13c1-e239-5efca27cf68c@erg.abdn.ac.uk> <CACL_3VHdyLAmzMbWsTVfJD+4tTzsMvcTzKS1B1CAdZ3k5U957g@mail.gmail.com> <CALx6S34DUrUBYd94LPPg4Hgh0FnZYZjZ4eKEYuaxb-7zbzb=pQ@mail.gmail.com> <CACL_3VEq9R=HmWXGbu_zcrgWfG0=q0z+HWM3cQ9Vh68hTCUR-w@mail.gmail.com> <CALx6S35bdGwY8FagGn8x5CaO4O3zW3U+NnB5ejC7bB6BHsXtJg@mail.gmail.com> <CACL_3VFwUJzT7uiXh33gBffboqqb51uFWJAEh290SsD0=aAzaQ@mail.gmail.com> <CALx6S34Lai=YS8i1VTC1zKHqsCTt_XUeKfwob7Qe_BA49bHC3A@mail.gmail.com>
In-Reply-To: <CALx6S34Lai=YS8i1VTC1zKHqsCTt_XUeKfwob7Qe_BA49bHC3A@mail.gmail.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Sun, 20 Jun 2021 16:36:18 -0700
X-Gmail-Original-Message-ID: <CACL_3VFZphux8uCqh6seVgTEjyjOhCjGd-jHtdGc0fR9opKWUg@mail.gmail.com>
Message-ID: <CACL_3VFZphux8uCqh6seVgTEjyjOhCjGd-jHtdGc0fR9opKWUg@mail.gmail.com>
To: Tom Herbert <tom@herbertland.com>
Cc: "C. M. Heard" <heard@pobox.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Joseph Touch <touch@strayalpha.com>, TSVWG <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b134aa05c53b06a0"
X-Pobox-Relay-ID: 56C91338-D220-11EB-BC8C-FD8818BA3BAF-06080547!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/thc0mIjU6CcyppULA1L0aV3Mk7M>
Subject: Re: [tsvwg] RDMA Support by UDP FRAG Option
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: Sun, 20 Jun 2021 23:36:42 -0000

On Sat, Jun 19, 2021 at 6:01 PM Tom Herbert wrote:

> On Sat, Jun 19, 2021 at 4:39 PM C. M. Heard wrote:
>
>> 2.) Assuming that the trailer checksum (OCS) is present, it is not clear
>> how offload for the inner packet checksum could be expected to work
>> properly without change. Remember, OCS does not cause the data in the
>> trailer to sum to zero. It causes it to sum to the ones-complement of the
>> trailer length.
>>
>> The modifications needed to handle point #2 are small -- specifically,
>> adding the trailer length to whatever would normally be preloaded into the
>> inner packet. The FRAG proposal
>> in draft-ietf-tsvwg-udp-options-13#section-5.5, which proposes to sandwich
>> the payload in between option headers, would make it a whole lot harder.
>>
>
> Protocol trailers are a fundamental problem. At this point it's not
> clear to me that there is a way to make them work correctly in all use
> cases with deployed HW.  Protocol headers, like those used per FRAG,
> shouldn't be a problem,


I believe that fear is unjustified. In every case analyzed in detail so far
-- including this one -- trailers involve only minor rework at most.  I
believe that I proved my case conclusively for the usual case (UDP used as
a straight transport, not as an encapsulation) in
https://mailarchive.ietf.org/arch/msg/tsvwg/RZULHOKRgrSYIvsI-5Hg7sNtSS8/.
Additionally, while an encapsulator that uses UDP options may need to be
modified in order to use hardware checksum offload, I think it's clear that
the modifications needed are bounded and small. Actually for the case of a
TCP inner packet the pseudo-header will be OK to use with a trailer that
has OCS included if instead of the actual RCP length the pseudo-header
includes TCP + trailer length. The driver still has to remember to copy
only UDP length - 8 bytes. Arguably, if it were written correctly in the
first place, it would be ready now.

The proposal in the -13 draft does have problems in this regard. I'll reply
to that thread in the next day or so with an explanation.

Thanks,

Mike Heard