From: Sergei Shtepa <sergei.shtepa@veeam.com>
To: <axboe@kernel.dk>, <linux-block@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Sergei Shtepa <sergei.shtepa@veeam.com>
Subject: [PATCH 18/20] block, blksnap: Kconfig
Date: Mon, 13 Jun 2022 18:53:11 +0300 [thread overview]
Message-ID: <1655135593-1900-19-git-send-email-sergei.shtepa@veeam.com> (raw)
In-Reply-To: <1655135593-1900-1-git-send-email-sergei.shtepa@veeam.com>
The module configuration file allows you to set default values for
module parameters.
Signed-off-by: Sergei Shtepa <sergei.shtepa@veeam.com>
---
drivers/block/blksnap/Kconfig | 101 ++++++++++++++++++++++++++++++++++
1 file changed, 101 insertions(+)
create mode 100644 drivers/block/blksnap/Kconfig
diff --git a/drivers/block/blksnap/Kconfig b/drivers/block/blksnap/Kconfig
new file mode 100644
index 000000000000..8588a89e30ad
--- /dev/null
+++ b/drivers/block/blksnap/Kconfig
@@ -0,0 +1,101 @@
+# SPDX-License-Identifier: GPL-2.0
+#
+# block io layer filter module configuration
+#
+#
+
+config BLK_SNAP
+ tristate "Block device snapshot and change tracker module"
+ depends on BLK_FILTER
+ help
+ Allow to create snapshots and track block changes for a block
+ devices. Designed for creating backups for any block devices
+ (without device mapper). Snapshots are temporary and are released
+ then backup is completed. Change block tracking allows you to
+ create incremental or differential backups.
+
+config BLK_SNAP_TRACKING_BLOCK_MINIMUM_SHIFT
+ depends on BLK_SNAP
+ int "The power of 2 for minimum trackings block size"
+ default 16
+ help
+ The minimum tracking block size by default is 64 KB (shift 16)
+ It's looks good for block device 128 GB or lower.
+ In this case, the block device is divided into 2097152 blocks.
+
+config BLK_SNAP_TRACKING_BLOCK_MAXIMUM_COUNT
+ depends on BLK_SNAP
+ int "The limit of the maximum number of trackings blocks"
+ default 2097152
+ help
+ As the size of the block device grows, the size of the tracking block
+ size should also grow. For this purpose, the limit of the maximum
+ number of block size is set.
+
+config BLK_SNAP_CHUNK_MINIMUM_SHIFT
+ depends on BLK_SNAP
+ int "The power of 2 for minimum snapshots chunk size"
+ default 18
+ help
+ The minimum chunk size by default is 256 KB (shift 18)
+ It's looks good for block device 128 GB or lower.
+ In this case, the block device is divided into 524288 chunks.
+
+config BLK_SNAP_CHUNK_MAXIMUM_COUNT
+ depends on BLK_SNAP
+ int "The limit of the maximum number of snapshots chunks"
+ default 2097152
+ help
+ As the size of the block device grows, the size of the chunk
+ should also grow. For this purpose, the limit of the maximum number
+ of chunks is set.
+
+config BLK_SNAP_CHUNK_MAXIMUM_IN_CACHE
+ depends on BLK_SNAP
+ int "The limit of the maximum chunks in memory cache"
+ default 64
+ help
+ Since reading and writing to snapshots is performed in large chunks,
+ a cache is implemented to optimize reading small portions of data
+ from the snapshot image. As the number of chunks in the cache
+ increases, memory consumption also increases.
+ The minimum recommended value is four.
+
+config BLK_SNAP_FREE_DIFF_BUFFER_POOL_SIZE
+ depends on BLK_SNAP
+ int "The maximum size of the free buffers pool"
+ default 128
+ help
+ A buffer can be allocated for each chunk. After use, this buffer is
+ not released immediately, but is sent to the pool of free buffers.
+ However, if there are too many free buffers in the pool, they are
+ released immediately. The maximum size of the pool is regulated by
+ this define.
+
+config BLK_SNAP_DIFF_STORAGE_MINIMUM
+ depends on BLK_SNAP
+ int "The minimum allowable size of the difference storage in sectors"
+ default 2097152
+ help
+ When reached, an event is generated about the lack of free space.
+
+config BLK_SNAP_DEBUG_MEMORY_LEAK
+ depends on BLK_SNAP
+ bool "Enable memory leak detector"
+ default n
+ help
+ Enables debugging code to monitor memory consumption by the module.
+
+ If unsure, say N.
+
+config BLK_SNAP_ALLOW_DIFF_STORAGE_IN_MEMORY
+ depends on BLK_SNAP
+ bool "Allow difference storage in memory"
+ default n
+ help
+ Enables the ability to create a repository of changes in memory.
+ This feature can be useful for debugging. Or it can be used for
+ mobile phones or other devices if there are guaranteed not to be
+ a large number of writings during the snapshot hold.
+
+ If unsure, say N.
--
2.20.1
next prev parent reply other threads:[~2022-06-13 18:57 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 15:52 [PATCH 00/20] blksnap - creating non-persistent snapshots for backup Sergei Shtepa
2022-06-13 15:52 ` [PATCH 01/20] block, blk_filter: enable block device filters Sergei Shtepa
2022-06-13 21:50 ` Randy Dunlap
2022-06-14 9:19 ` Sergei Shtepa
2022-06-14 9:21 ` Sergei Shtepa
2022-06-14 9:01 ` kernel test robot
2022-07-06 12:59 ` Christoph Hellwig
2022-07-07 8:26 ` Sergei Shtepa
2022-07-07 17:26 ` Christoph Hellwig
2022-07-08 10:45 ` Sergei Shtepa
2022-07-13 11:56 ` Christoph Hellwig
2022-07-13 13:47 ` Sergei Shtepa
2022-07-14 5:12 ` Christoph Hellwig
2022-07-14 9:22 ` Sergei Shtepa
2022-06-13 15:52 ` [PATCH 02/20] block, blksnap: header file of the module interface Sergei Shtepa
2022-07-06 13:03 ` Christoph Hellwig
2022-06-13 15:52 ` [PATCH 03/20] block, blksnap: module management interface functions Sergei Shtepa
2022-06-13 22:44 ` Chaitanya Kulkarni
2022-06-13 15:52 ` [PATCH 04/20] block, blksnap: init() and exit() functions Sergei Shtepa
2022-06-13 15:52 ` [PATCH 05/20] block, blksnap: interaction with sysfs Sergei Shtepa
2022-06-13 15:52 ` [PATCH 06/20] block, blksnap: attaching and detaching the filter and handling a bios Sergei Shtepa
2022-06-13 15:53 ` [PATCH 07/20] block, blksnap: map of change block tracking Sergei Shtepa
2022-06-13 15:53 ` [PATCH 08/20] block, blksnap: big buffer in the form of an array of pages Sergei Shtepa
2022-07-06 13:09 ` Christoph Hellwig
2022-06-13 15:53 ` [PATCH 09/20] block, blksnap: minimum data storage unit of the original block device Sergei Shtepa
2022-06-13 15:53 ` [PATCH 10/20] block, blksnap: buffer in memory for the minimum data storage unit Sergei Shtepa
2022-06-13 15:53 ` [PATCH 11/20] block, blksnap: functions and structures for performing block I/O operations Sergei Shtepa
2022-07-07 17:33 ` Christoph Hellwig
2022-06-13 15:53 ` [PATCH 12/20] block, blksnap: storage for storing difference blocks Sergei Shtepa
2022-06-13 15:53 ` [PATCH 13/20] block, blksnap: event queue from the difference storage Sergei Shtepa
2022-06-13 15:53 ` [PATCH 14/20] block, blksnap: owner of information about overwritten blocks of the original block device Sergei Shtepa
2022-06-13 15:53 ` [PATCH 15/20] block, blksnap: snapshot image " Sergei Shtepa
2022-07-06 13:13 ` Christoph Hellwig
2022-07-07 9:16 ` Sergei Shtepa
2022-07-07 17:24 ` Christoph Hellwig
2022-07-08 7:58 ` Sergei Shtepa
2022-07-08 8:04 ` Christoph Hellwig
2022-06-13 15:53 ` [PATCH 16/20] block, blksnap: snapshot Sergei Shtepa
2022-06-13 15:53 ` [PATCH 17/20] block, blksnap: debugging mechanism for monitoring memory consumption Sergei Shtepa
2022-06-13 15:53 ` Sergei Shtepa [this message]
2022-06-13 21:38 ` [PATCH 18/20] block, blksnap: Kconfig Randy Dunlap
2022-07-06 13:06 ` Christoph Hellwig
2022-06-13 15:53 ` [PATCH 19/20] block, blksnap: Makefile Sergei Shtepa
2022-07-06 13:06 ` Christoph Hellwig
2022-06-13 15:53 ` [PATCH 20/20] block, blksnap: adds a blksnap to the kernel tree Sergei Shtepa
2022-06-18 2:11 ` kernel test robot
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=1655135593-1900-19-git-send-email-sergei.shtepa@veeam.com \
--to=sergei.shtepa@veeam.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®