From: Russell Harmon <eatnumber1@gmail.com> To: bagasdotme@gmail.com Cc: mpatocka@redhat.com, snitzer@redhat.com, dm-devel@redhat.com, linux-doc@vger.kernel.org, Russell Harmon <eatnumber1@gmail.com> Subject: [PATCH v3 4/4] Document an example of how the tunables relate in dm-integrity. Date: Sun, 4 Jun 2023 12:06:04 -0700 [thread overview] Message-ID: <20230604190604.4800-5-eatnumber1@gmail.com> (raw) In-Reply-To: <20230604190604.4800-1-eatnumber1@gmail.com> For example, on a device using the default interleave_sectors of 32768, a block_size of 512, and an internal_hash of crc32c with a tag size of 4 bytes, it will take 128 KiB of tags to track a full data area, requiring 256 sectors of metadata per data area. With the default buffer_sectors of 128, that means there will be 2 buffers per metadata area, or 2 buffers per 16 MiB of data. Signed-off-by: Russell Harmon <eatnumber1@gmail.com> --- Documentation/admin-guide/device-mapper/dm-integrity.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Documentation/admin-guide/device-mapper/dm-integrity.rst b/Documentation/admin-guide/device-mapper/dm-integrity.rst index 0241457c0027..d8a5f14d0e3c 100644 --- a/Documentation/admin-guide/device-mapper/dm-integrity.rst +++ b/Documentation/admin-guide/device-mapper/dm-integrity.rst @@ -213,6 +213,12 @@ table and swap the tables with suspend and resume). The other arguments should not be changed when reloading the target because the layout of disk data depend on them and the reloaded target would be non-functional. +For example, on a device using the default interleave_sectors of 32768, a +block_size of 512, and an internal_hash of crc32c with a tag size of 4 +bytes, it will take 128 KiB of tags to track a full data area, requiring +256 sectors of metadata per data area. With the default buffer_sectors of +128, that means there will be 2 buffers per metadata area, or 2 buffers +per 16 MiB of data. Status line: -- 2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: Russell Harmon <eatnumber1@gmail.com> To: bagasdotme@gmail.com Cc: Russell Harmon <eatnumber1@gmail.com>, dm-devel@redhat.com, mpatocka@redhat.com, snitzer@redhat.com, linux-doc@vger.kernel.org Subject: [dm-devel] [PATCH v3 4/4] Document an example of how the tunables relate in dm-integrity. Date: Sun, 4 Jun 2023 12:06:04 -0700 [thread overview] Message-ID: <20230604190604.4800-5-eatnumber1@gmail.com> (raw) In-Reply-To: <20230604190604.4800-1-eatnumber1@gmail.com> For example, on a device using the default interleave_sectors of 32768, a block_size of 512, and an internal_hash of crc32c with a tag size of 4 bytes, it will take 128 KiB of tags to track a full data area, requiring 256 sectors of metadata per data area. With the default buffer_sectors of 128, that means there will be 2 buffers per metadata area, or 2 buffers per 16 MiB of data. Signed-off-by: Russell Harmon <eatnumber1@gmail.com> --- Documentation/admin-guide/device-mapper/dm-integrity.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Documentation/admin-guide/device-mapper/dm-integrity.rst b/Documentation/admin-guide/device-mapper/dm-integrity.rst index 0241457c0027..d8a5f14d0e3c 100644 --- a/Documentation/admin-guide/device-mapper/dm-integrity.rst +++ b/Documentation/admin-guide/device-mapper/dm-integrity.rst @@ -213,6 +213,12 @@ table and swap the tables with suspend and resume). The other arguments should not be changed when reloading the target because the layout of disk data depend on them and the reloaded target would be non-functional. +For example, on a device using the default interleave_sectors of 32768, a +block_size of 512, and an internal_hash of crc32c with a tag size of 4 +bytes, it will take 128 KiB of tags to track a full data area, requiring +256 sectors of metadata per data area. With the default buffer_sectors of +128, that means there will be 2 buffers per metadata area, or 2 buffers +per 16 MiB of data. Status line: -- 2.34.1 -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2023-06-04 19:06 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-30 0:20 [dm-devel] [PATCH] Improve the dm-integrity documentation Russell Harmon 2023-06-03 10:02 ` Russell Harmon 2023-06-03 12:50 ` Bagas Sanjaya 2023-06-03 12:50 ` Bagas Sanjaya 2023-06-03 12:45 ` Bagas Sanjaya 2023-06-03 12:45 ` Bagas Sanjaya 2023-06-03 20:15 ` Russell Harmon 2023-06-03 20:15 ` [dm-devel] " Russell Harmon 2023-06-03 20:15 ` [PATCH 1/4] Fix minor grammatical error in dm-integrity.rst Russell Harmon 2023-06-03 20:15 ` [dm-devel] " Russell Harmon 2023-06-03 20:15 ` [PATCH 2/4] Documents the meaning of "buffer" in dm-integrity Russell Harmon 2023-06-03 20:15 ` [dm-devel] " Russell Harmon 2023-06-03 20:15 ` [PATCH 3/4] Document dm-integrity default values Russell Harmon 2023-06-03 20:15 ` [dm-devel] " Russell Harmon 2023-06-03 20:15 ` [PATCH 4/4] Document an example of how the tunables relate in dm-integrity Russell Harmon 2023-06-03 20:15 ` [dm-devel] " Russell Harmon 2023-06-04 14:07 ` [PATCH] Improve the dm-integrity documentation Bagas Sanjaya 2023-06-04 14:07 ` [dm-devel] " Bagas Sanjaya 2023-06-04 18:25 ` Russell Harmon 2023-06-04 18:25 ` [dm-devel] " Russell Harmon 2023-06-04 19:06 ` [PATCH v3 0/4] " Russell Harmon 2023-06-04 19:06 ` [dm-devel] " Russell Harmon 2023-06-04 19:06 ` [PATCH v3 1/4] Fix minor grammatical error in dm-integrity.rst Russell Harmon 2023-06-04 19:06 ` [dm-devel] " Russell Harmon 2023-06-05 3:03 ` Bagas Sanjaya 2023-06-05 3:03 ` [dm-devel] " Bagas Sanjaya 2023-06-05 5:00 ` Russell Harmon 2023-06-05 5:00 ` [dm-devel] " Russell Harmon 2023-06-04 19:06 ` [PATCH v3 2/4] Documents the meaning of "buffer" in dm-integrity Russell Harmon 2023-06-04 19:06 ` [dm-devel] " Russell Harmon 2023-06-05 3:05 ` Bagas Sanjaya 2023-06-05 3:05 ` [dm-devel] " Bagas Sanjaya 2023-06-05 3:07 ` Bagas Sanjaya 2023-06-05 3:07 ` [dm-devel] " Bagas Sanjaya 2023-06-05 5:01 ` Russell Harmon 2023-06-05 5:01 ` [dm-devel] " Russell Harmon 2023-06-04 19:06 ` [PATCH v3 3/4] Document dm-integrity default values Russell Harmon 2023-06-04 19:06 ` [dm-devel] " Russell Harmon 2023-06-05 3:16 ` Bagas Sanjaya 2023-06-05 3:16 ` [dm-devel] " Bagas Sanjaya 2023-06-05 5:05 ` Russell Harmon 2023-06-05 5:05 ` [dm-devel] " Russell Harmon 2023-06-05 13:23 ` Jonathan Corbet 2023-06-05 13:23 ` [dm-devel] " Jonathan Corbet 2023-06-06 2:16 ` Bagas Sanjaya 2023-06-06 2:16 ` [dm-devel] " Bagas Sanjaya 2023-06-04 19:06 ` Russell Harmon [this message] 2023-06-04 19:06 ` [dm-devel] [PATCH v3 4/4] Document an example of how the tunables relate in dm-integrity Russell Harmon 2023-06-05 3:17 ` Bagas Sanjaya 2023-06-05 3:17 ` [dm-devel] " Bagas Sanjaya 2023-06-05 5:05 ` Russell Harmon 2023-06-05 5:05 ` [dm-devel] " Russell Harmon 2023-06-05 5:08 ` [PATCH v4 0/4] Improve the dm-integrity documentation Russell Harmon 2023-06-05 5:08 ` [dm-devel] " Russell Harmon 2023-06-05 5:08 ` [PATCH v4 1/4] Documentation: dm-integrity: Fix minor grammatical error Russell Harmon 2023-06-05 5:08 ` [dm-devel] " Russell Harmon 2023-06-06 2:17 ` Bagas Sanjaya 2023-06-06 2:17 ` [dm-devel] " Bagas Sanjaya 2023-06-05 5:08 ` [PATCH v4 2/4] Documentation: dm-integrity: Document the meaning of "buffer" Russell Harmon 2023-06-05 5:08 ` [dm-devel] " Russell Harmon 2023-06-06 2:18 ` Bagas Sanjaya 2023-06-06 2:18 ` [dm-devel] " Bagas Sanjaya 2023-06-05 5:08 ` [PATCH v4 3/4] Documentation: dm-integrity: Document default values Russell Harmon 2023-06-05 5:08 ` [dm-devel] " Russell Harmon 2023-06-05 5:08 ` [PATCH v4 4/4] Documentation: dm-integrity: Document an example of how the tunables relate Russell Harmon 2023-06-05 5:08 ` [dm-devel] " Russell Harmon 2023-06-17 19:37 ` Russell Harmon 2023-06-17 19:37 ` [dm-devel] " Russell Harmon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230604190604.4800-5-eatnumber1@gmail.com \ --to=eatnumber1@gmail.com \ --cc=bagasdotme@gmail.com \ --cc=dm-devel@redhat.com \ --cc=linux-doc@vger.kernel.org \ --cc=mpatocka@redhat.com \ --cc=snitzer@redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.