From nobody Sun Jan 12 21:17:51 2025 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YWSsn6Xkpz5jqZh for ; Sun, 12 Jan 2025 21:18:05 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ej1-f43.google.com (mail-ej1-f43.google.com [209.85.218.43]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YWSsm6vfsz4Z6y for ; Sun, 12 Jan 2025 21:18:04 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.218.43 as permitted sender) smtp.mailfrom=asomers@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none) Received: by mail-ej1-f43.google.com with SMTP id a640c23a62f3a-aaecf50578eso728000266b.2 for ; Sun, 12 Jan 2025 13:18:04 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736716683; x=1737321483; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=jCyTK2Ksr3Ac5G1vMuPh61XTf2vq7MA3ET6lqNvlNLI=; b=Nu7OE7cJ3UmIiTcr/i5IZIWaQACdIm28lDELdo3dkV5qS6gqEt9s16utSwbVRXHG1x VrxadgER9HdZlIgOgNN1WmWSZ/LRkDLryQBNi5KzKXzZIygcCxWuw5fzG1K6EBLHOhs2 Bmg0vmXnSngsfSur2VzEl1UfFTC3Ett91qJODEylxi7vnM+xl1zD9GVO510mYeNcB2IS KhPCW0pxUsezcqcsJkmXJWCp7h5oy1ErI1LJvRHNpVkRmxE1f+YTNAhCC01CG7lgkcRL jyKuGnEcRUIHfo2zhA9QdGppyXVkKOrm3s4BQKbTJkbVrgqRjrLhA/cbkS73uKg25fnO NKow== X-Gm-Message-State: AOJu0Yw5srWuxPZXAHu1dD/waxn92ZkDr9NLaWpS4RypbptMndL0kOPD mDgBvfJpbIswND6/B8getpUtciqJzJQaxPeZxRcwvun0VDxKe3TAZwi4PZGczD+gk/H8JF5Nofq JEDWylNuKCHRNX+2CrIvylNeZkq0Hlw== X-Gm-Gg: ASbGnctzPxfPR29CoFJuTJvPXSPJx7v31LeaeL23Jx35BLpwoVHpV/s204QoMNfE9z+ k33LWFpStJCtQFfkmSHKSP7MF8vRHT8gKsPB0hQ== X-Google-Smtp-Source: AGHT+IFZy5A7DljZCEWuzp4v6XfxtjzE7gLjTRBzb+3LBXJTHTYwjDgLjZ2IkoVx8IQ2bKb8VN/MHa0S5Zrm+/v+nrA= X-Received: by 2002:a17:907:72d6:b0:aa6:88c6:9449 with SMTP id a640c23a62f3a-ab2ab56abc5mr1857465866b.19.1736716682744; Sun, 12 Jan 2025 13:18:02 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Alan Somers Date: Sun, 12 Jan 2025 14:17:51 -0700 X-Gm-Features: AbW1kvYIamTYQyiwxUD0cfLCDBul2RZakbB_vqvQW8Ivg2QDuB--h4-MUfMuxWo Message-ID: Subject: Re: WRITE_SAME support in FreeBSD nfsd NFSv4.1 mode? To: Cedric Blancher Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4YWSsm6vfsz4Z6y X-Spamd-Bar: - X-Spamd-Result: default: False [-1.08 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.67)[-0.673]; NEURAL_HAM_SHORT(-0.51)[-0.509]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; MIME_GOOD(-0.10)[text/plain]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_TO(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FREEFALL_USER(0.00)[asomers]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.218.43:from]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TAGGED_RCPT(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.218.43:from] On Sun, Jan 12, 2025 at 12:23=E2=80=AFAM Cedric Blancher wrote: > > On Fri, 10 Jan 2025 at 16:02, Alan Somers wrote: > > > > On Thu, Jan 9, 2025 at 5:31=E2=80=AFPM Dan Shelton wrote: > > > > > > Hello! > > > > > > Does FreeBSD nfsd support the WRITE_SAME request in NFSv4.1 mode? > > > > > > Dan > > > -- > > > Dan Shelton - Cluster Specialist Win/Lin/Bsd > > > > Out of curiosity, what is your use case? > > As discussed in the linux-nfs@ list, is a typical "big data" and > database accelerator, for example fast pattern fill (1 WRITE_SAME > command over the write, compared to commands with data block, > where is typically > 200 average), or just zero fill for blocks. > It's basically reducing network traffic dramatically. > > Windows SMB 3.0 already supports that, and is a main selling point for > M$ to keep database people on the W$ platform. They even added several > Windows syscalls like > https://learn.microsoft.com/en-us/windows/win32/api/winioctl/ni-winioctl-= fsctl_set_zero_data > > Ced I understand why WRITE SAME would greatly reduce network traffic compared to writing the same data n times. But my question is, what real application requires that, where the data isn't simply all-zeros? Are there database operations that require writing the same non-zero pattern to multiple blocks?