[nfsv4] Erasure coding vs delegations
Rick Macklem <rick.macklem@gmail.com> Wed, 04 December 2024 21:05 UTC
Return-Path: <rick.macklem@gmail.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CC73C1D4CCC for <nfsv4@ietfa.amsl.com>; Wed, 4 Dec 2024 13:05:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CwfQ43SMCX5I for <nfsv4@ietfa.amsl.com>; Wed, 4 Dec 2024 13:05:51 -0800 (PST)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDDC8C15154F for <nfsv4@ietf.org>; Wed, 4 Dec 2024 13:04:38 -0800 (PST)
Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-5d11413b633so138008a12.2 for <nfsv4@ietf.org>; Wed, 04 Dec 2024 13:04:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733346277; x=1733951077; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=JBbg2e6F2KJsTNPk9Gw8kEpSsT8PVny9JvsrCHXpiOg=; b=git3lXc8svONYSu0zHwFH0pGJCXsrA7NiKYQOvQ/DXaNuBoixnQW9qxC10rwnwXAPD wW9mgk0dP/1mWCu0D+eMkvNHdBUQpOqdzkAwzR2NjI8Y0JDT+0XKdkGhouMHvMwKrb7E SBO4WgoshksC5CegefcMtDSw96rXGG5slMnxqVOt/tiB1xzXDPuYtsyrowIumaKYt7ik kSbU2sR3h2bFf41oi58JugSj+daHBqVSirgoxakWAbpm71uz8/0vL/u1Sq6GxMT6+cmP /PURoBocZxRyDymo9SCSapl46m4M8CvBq3it11Kx5XRVE45mMnVkUjIJ4EvCKaHV9kqu P/Vw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733346277; x=1733951077; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=JBbg2e6F2KJsTNPk9Gw8kEpSsT8PVny9JvsrCHXpiOg=; b=bhbZRjr8ld5ynhplPFzU14OOdX++mHY0tZgZhRqoxPqAWXf8VHeybNQPuLIDzirz9v VdbcI6glXllKwtrYlzoOfxS1W0K1g3FDjtatXB2Zn9VNdG1+zja9lSKQNuhAdE89IHCh TddCsw97QGy2nXMl6iJYPXdQf9K4LyZdQVTS78QT7Xlou5S7/rhxbT5ADEXKyuFkK+LS 4Lx8CJ9keL3ej2zKZG+1ZGf2N7oTmsWqgqP+1kCoSwyTprELvcGJAwfesatvEnbNJVWf Q8QiDy11XBRq9BL7VNa9XVftLzxMjnMwUkCskOGuYMKknM+hd/4T5Csk8K7219Jm5cvP 2Nkg==
X-Gm-Message-State: AOJu0Yy48Luq07cQjh533pnkI0fet57dORSe4GY+WPMw0XpZAtmLUsTt tDPhOEhXlak7YE00kCIpw00XtjjTmJDpEU9nMunnW6el1HL0D5oCRyzbNHhcTvRPyKM2CNz8N18 x0jdZilDSMWg8sXFl+HhieCnrZ+Eh
X-Gm-Gg: ASbGncv1pnmvqpw5gkpn0fVflKunBxXw7Q2AGsPtIpyheIkEWld2L3TzB8YEo4wxdzQ 6CwE3QEaRKJ1xbgSPhK9NjzKG+jqq7tonLdJYVfBpqxrVucwHhO1cAC/ijCI2QNA=
X-Google-Smtp-Source: AGHT+IHZ+nCAb3VKjVPj8N5QFHJGYf2C8ZFSuCxNZ1QiTXBYDHKi34kU720LAzcMePU8w6QDKDWCymWRHZMROLwb+ws=
X-Received: by 2002:a05:6402:210c:b0:5cf:9e5:7d20 with SMTP id 4fb4d7f45d1cf-5d10cb5b94emr6386522a12.17.1733346277136; Wed, 04 Dec 2024 13:04:37 -0800 (PST)
MIME-Version: 1.0
From: Rick Macklem <rick.macklem@gmail.com>
Date: Wed, 04 Dec 2024 13:04:27 -0800
Message-ID: <CAM5tNy55waUSdLmRFXz5OvUhSe1pok0GJ62+drPbDvp3eBjcyg@mail.gmail.com>
To: NFSv4 <nfsv4@ietf.org>, Thomas Haynes <loghyr@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Message-ID-Hash: IVFRJ3Z3AHM4BKU7ZB7RXNL3VUWUMFNJ
X-Message-ID-Hash: IVFRJ3Z3AHM4BKU7ZB7RXNL3VUWUMFNJ
X-MailFrom: rick.macklem@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-nfsv4.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [nfsv4] Erasure coding vs delegations
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/pYMMNCLInP54_VriSwAhx-hHtmQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Owner: <mailto:nfsv4-owner@ietf.org>
List-Post: <mailto:nfsv4@ietf.org>
List-Subscribe: <mailto:nfsv4-join@ietf.org>
List-Unsubscribe: <mailto:nfsv4-leave@ietf.org>
Hi, A simple comment w.r.t. Tom's talk to-day on Erasure coding. I'll admit I have not read your draft, but I was wondering if you have looked at the relationship between your erasure encoding work and delegations? In particular, a write delegation issued by the MDS to a client would ensure exclusive writing and, as such, issuing write delegations "generously" might reduce your write contention problem? Just a thought, rick
- [nfsv4] Erasure coding vs delegations Rick Macklem
- [nfsv4] Re: Erasure coding vs delegations Thomas Haynes
- [nfsv4] Re: Erasure coding vs delegations Rick Macklem