From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-12.8 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 42D6DC433DF for ; Mon, 20 Jul 2020 08:52:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2170722B4D for ; Mon, 20 Jul 2020 08:52:15 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=wdc.com header.i=@wdc.com header.b="oPANTfs2" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728063AbgGTIwO (ORCPT ); Mon, 20 Jul 2020 04:52:14 -0400 Received: from esa1.hgst.iphmx.com ([68.232.141.245]:15088 "EHLO esa1.hgst.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726938AbgGTIwO (ORCPT ); Mon, 20 Jul 2020 04:52:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=wdc.com; i=@wdc.com; q=dns/txt; s=dkim.wdc.com; t=1595235133; x=1626771133; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=KALZF4NqHXC9qoy6I4teMnQITGGpyunub/V7H6Pi3g4=; b=oPANTfs22BQxK2y4m0Bj5aRrx80d1lizvP65Ffh+QsU75pkXuPD6+MFa oTmggdOyNwsaUnvDdHMYyztbdngxe/kITnv9XtU6de+tqPVyRvL3Ghk8d 4jov/gV33zr7wCuKt87HATRnSrL3yfird+/Obpw8ub7EEwY6jLQe7tKLU rZuVttz1vV8weqdZgn7L1Efwl3kbtoKaK2aQGp4kC8RGsK/FtS6fUV1cJ ba3ZXBFfcgyU9MqwQc6EjdwKOzjMbct9wslsl/YkFUhcdZbXh6LYvvONa kEwJoK3OrJZgkMieySmSdxwuLP0udzj6pqPys662I2OspJWu2QnMGo8t0 Q==; IronPort-SDR: q3Vmvu6m+G8+4SusyKN3FMc5rqj6pV/XrebSq0iq9xg8XGaT93Vgfm7OJFv4DrZInzKsyh2xPe ohdBtTDNY01jJRxnX+bDXgEJ7tQDAS6dZQimDj2/6SQuGUAL9EKl70DpTpnMvl8rusHl+MUC4v fnPn7tW5te2mDTX1cV1Vy/IerbXtMkPEDbV0Sxhq0IqCPN1t8XC73paMbzGTCJ6/tJlRZPnLJG Tk6KOhCZt3re+bi539ngB2isO5MOwBHbmw08j+lAQfiRvHyTuromXDK8UT0WoGLfLd53tVl45w wrQ= X-IronPort-AV: E=Sophos;i="5.75,374,1589212800"; d="scan'208";a="252171863" Received: from h199-255-45-14.hgst.com (HELO uls-op-cesaep01.wdc.com) ([199.255.45.14]) by ob1.hgst.iphmx.com with ESMTP; 20 Jul 2020 16:52:13 +0800 IronPort-SDR: goV+rds3anDk53ybGwIvHtsgyVYGo3pT3kUIvtolHUq5UHxlLyPzOc5YwGDkc/kTwioggSsGjC uKb2MXZc9gi+U/LsfpPmAl4PW3AVaGsok= Received: from uls-op-cesaip02.wdc.com ([10.248.3.37]) by uls-op-cesaep01.wdc.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Jul 2020 01:40:32 -0700 IronPort-SDR: eLy2mmeZYrbtTd31IZ98bnUygnyRRcUBp2j6uCsYXu+E8/rvjc6HVyeuCirvKo8LLJT1iwlvaF mFo9PdompHyQ== WDCIronportException: Internal Received: from unknown (HELO redsun60.ssa.fujisawa.hgst.com) ([10.149.66.36]) by uls-op-cesaip02.wdc.com with ESMTP; 20 Jul 2020 01:52:13 -0700 From: Johannes Thumshirn To: Damien Le Moal Cc: linux-fsdevel@vger.kernel.org, Johannes Thumshirn Subject: [PATCH v2 2/2] zonefs: update documentation to reflect zone size vs capacity Date: Mon, 20 Jul 2020 17:52:08 +0900 Message-Id: <20200720085208.27347-3-johannes.thumshirn@wdc.com> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200720085208.27347-1-johannes.thumshirn@wdc.com> References: <20200720085208.27347-1-johannes.thumshirn@wdc.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org Update the zonefs documentation to reflect the difference between a zone's size and it's capacity. The maximum file size in zonefs is the zones capacity, for ZBC and ZAC based devices, which do not have a separate zone capacity, the zone capacity is equal to the zone size. Signed-off-by: Johannes Thumshirn --- Documentation/filesystems/zonefs.rst | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/Documentation/filesystems/zonefs.rst b/Documentation/filesystems/zonefs.rst index 71d845c6a700..6c18bc8ce332 100644 --- a/Documentation/filesystems/zonefs.rst +++ b/Documentation/filesystems/zonefs.rst @@ -110,14 +110,14 @@ contain files named "0", "1", "2", ... The file numbers also represent increasing zone start sector on the device. All read and write operations to zone files are not allowed beyond the file -maximum size, that is, beyond the zone size. Any access exceeding the zone -size is failed with the -EFBIG error. +maximum size, that is, beyond the zone capacity. Any access exceeding the zone +capacity is failed with the -EFBIG error. Creating, deleting, renaming or modifying any attribute of files and sub-directories is not allowed. The number of blocks of a file as reported by stat() and fstat() indicates the -size of the file zone, or in other words, the maximum file size. +capacity of the zone file, or in other words, the maximum file size. Conventional zone files ----------------------- @@ -156,8 +156,8 @@ all accepted. Truncating sequential zone files is allowed only down to 0, in which case, the zone is reset to rewind the file zone write pointer position to the start of -the zone, or up to the zone size, in which case the file's zone is transitioned -to the FULL state (finish zone operation). +the zone, or up to the zone capacity, in which case the file's zone is +transitioned to the FULL state (finish zone operation). Format options -------------- @@ -324,7 +324,7 @@ file size set to 0. This is necessary as the write pointer of read-only zones is defined as invalib by the ZBC and ZAC standards, making it impossible to discover the amount of data that has been written to the zone. In the case of a read-only zone discovered at run-time, as indicated in the previous section. -the size of the zone file is left unchanged from its last updated value. +The size of the zone file is left unchanged from its last updated value. Zonefs User Space Tools ======================= @@ -401,8 +401,9 @@ append-writes to the file:: # ls -l /mnt/seq/0 -rw-r----- 1 root root 0 Nov 25 13:49 /mnt/seq/0 -Since files are statically mapped to zones on the disk, the number of blocks of -a file as reported by stat() and fstat() indicates the size of the file zone:: +Since files are statically mapped to zones on the disk, the number of blocks +of a file as reported by stat() and fstat() indicates the capacity of the file +zone:: # stat /mnt/seq/0 File: /mnt/seq/0 @@ -416,5 +417,6 @@ a file as reported by stat() and fstat() indicates the size of the file zone:: The number of blocks of the file ("Blocks") in units of 512B blocks gives the maximum file size of 524288 * 512 B = 256 MB, corresponding to the device zone -size in this example. Of note is that the "IO block" field always indicates the -minimum I/O size for writes and corresponds to the device physical sector size. +capacity in this example. Of note is that the "IO block" field always +indicates the minimum I/O size for writes and corresponds to the device +physical sector size. -- 2.26.2