Re: [tsvwg] RDMA Support by UDP FRAG Option

Tom Herbert <tom@herbertland.com> Thu, 17 June 2021 00:48 UTC

Return-Path: <tom@herbertland.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 1BEFA3A106F for <tsvwg@ietfa.amsl.com>; Wed, 16 Jun 2021 17:48:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-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 SikdSIp4DZgb for <tsvwg@ietfa.amsl.com>; Wed, 16 Jun 2021 17:48:35 -0700 (PDT)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 BEF753A106A for <tsvwg@ietf.org>; Wed, 16 Jun 2021 17:48:35 -0700 (PDT)
Received: by mail-ed1-x534.google.com with SMTP id n20so1510869edv.8 for <tsvwg@ietf.org>; Wed, 16 Jun 2021 17:48:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=msSE9udwD0iRVIDF+J2Uyq8in4pdS/nUCocMKxfuT9Q=; b=M2YfvNG4PyO3846b/mz0rX4AZ692/VriHOQ9euaFnLdFBWZ+U/mqRcX+zOj2ckiFb+ CV7fVWiX6K7Aboei0mvdHKYagTUFUjpu9FeMH7AUPX9Ev76lGK6W2gEriy+e83wnCHeR JE0Nr7cVguDcS4NMrZ/82ENxt/1pSWQ5LNwxX2p8vurI1SJ4UiNULKvwLB2+thyy26i6 pL643g7e/m+WtrLaE/9A2rxQ9b1sti2mAukZFIfLuIDFtHxXE/Yfuy2TBj3O6aFwlpJo UILUBT3R2B3NrnlQMFHRT9KN0hMHF+7kBxUuYWxJNUysLOBtUMuU80lmEABeWLC3r+/X qFng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=msSE9udwD0iRVIDF+J2Uyq8in4pdS/nUCocMKxfuT9Q=; b=SqS/gtJ3tTyMZubZ5dkPhWYSu7xj5QkEsgM94KJzw6Qntm38NQcNeqDBaVT/oDfsQH W3AkBRV2dVzxJbyAmuy38iGfmhUOB8kq6dTE/AmrQaq3SJKe40OTDS7jtH+ClI7Dbr5n FP5UjzL6aFR6TFMFKxgMtfC9DBLyImwTopAz83rQTEBA6td2PlU5Hfr4EdB7t49KBgey dcbfNaEyhORkgXNJHOAPx8RypCmU1askM7OIVNs7bPMxLwqjUuh5DZNXcTLH6HH01J9X P3uvkyaY3VyViNpKZHea2/ORztC0W43u9s8i/6jMbZkzfHqakkD81B0z7zyOERoa96wM nmBQ==
X-Gm-Message-State: AOAM531H2h5dqFWDsXAF5y55AnuHXvLnnUGt05tYpixO6MYoKwGauy9+ BokLTsBhTtI483FCWw4GZR80TLVwbL2zC0qHml4HMw==
X-Google-Smtp-Source: ABdhPJxHnFZxmGVP7y1aSX9/+J1YKZXmWshrnKYT09nK1TY4n457138P/Z6c2FfQNj55fSK15LZYwobaFayo7yNFJ54=
X-Received: by 2002:a05:6402:268f:: with SMTP id w15mr2998545edd.228.1623890913407; Wed, 16 Jun 2021 17:48:33 -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>
In-Reply-To: <7C51D926-9DBB-41F5-93B2-10F716F672B1@strayalpha.com>
From: Tom Herbert <tom@herbertland.com>
Date: Wed, 16 Jun 2021 17:48:21 -0700
Message-ID: <CALx6S37uN8TsXQZ3cv5jmxwxSyBRjK=-GQ_MsWxPWSs21XoGHw@mail.gmail.com>
To: Joseph Touch <touch@strayalpha.com>
Cc: TSVWG <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000c466c05c4eb9112"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/gKf6adWpk3cVsznUZpYDU6P8G6M>
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: Thu, 17 Jun 2021 00:48:41 -0000

On Wed, Jun 16, 2021, 5:16 PM Joseph Touch <touch@strayalpha.com> wrote:

>
>
> > On Jun 16, 2021, at 10:16 AM, Tom Herbert <tom@herbertland.com> wrote:
> >
> >> ...
> >> The idea is that the data can be placed directly in memory, with the
> last 3 bytes overwriting the first three. By moving only the space covered
> by the options, direct data placement can be used:
> >>
> >> 123de - write up to the last 3 bytes
> >> a23de - overwrite the last 3 bytes starting at the beginning (next 2
> lines too)
> >
> > That presumes that the memory holding the payload is writeable which
> > is not always true. For instance, that would not be the case if the
> > device DMAs the data into GPU memory.
>
> This approach is already OBE and thus not relevant.
>

What does OBE mean?

However, the approach above remains an expectation of any DMA transfer -
> there are always edge aspects that need to be adjusted, whether by a
> separate DMA or some other mechanism. It doesn’t have to be one byte at a
> time, as shown above.
>
> Joe
>
>